DataWorks has specific billing rules and overdue payment policies for its pay-as-you-go products. This topic describes these rules and policies.
Limitations
The billing rules and overdue payment policies described in this topic apply only to DataWorks pay-as-you-go products.
Billing and overdue payments
Alibaba Cloud provides service suspension protection. If you have an overdue payment for a pay-as-you-go resource, you can continue to use the Alibaba Cloud service for a specific period or up to a specific amount. You are charged for your usage during the service suspension protection period. The protection is not an upper limit for the total overdue payment. The period or amount of your service suspension protection is automatically calculated and updated each month based on your historical consumption on Alibaba Cloud. For more information, see Service suspension protection for overdue payments.
The following tables describe the billing rules and overdue payment policies for pay-as-you-go products.
|
Billed object |
Billing cycle |
Billing details |
Overdue payment details |
|
Serverless resource group (pay-as-you-go) |
Daily |
Each day, a bill is generated for the previous day's CU usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Serverless resource groups. |
|
|
Number of scheduled instances |
Daily |
Each day, a bill is generated based on the number of successfully run instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for task scheduling. |
|
|
Shared resource group for DataService Studio |
Hourly |
Each hour, a bill is generated for the previous hour's usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for shared resource groups for DataService Studio. |
|
|
Data Integration Internet traffic |
Hourly |
Each hour, a bill is generated for the previous hour's usage. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Internet traffic. |
|
|
Data Quality instance |
Daily |
Each day, a bill is generated based on the number of successfully run instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for Data Quality instances. Note
|
|
|
Intelligent baseline instance |
Daily |
Each day, a bill is generated based on the number of enabled baseline instances from the previous day. The corresponding balance is frozen mid-month. The actual fee is deducted after the final bill is generated at the beginning of the next month. For more information about pricing, see Billing for intelligent baseline instances. Note
|
|
|
Alert text messages and phone calls |
Daily |
Not applicable |
Not applicable |
|
OpenAPI calls |
Daily |
Not applicable |
If your account has an overdue payment, the service is immediately suspended. To avoid business interruptions, renew your service promptly. |