Charges and overdue payments for DataWorks pay-as-you-go products-DataWorks(DataWorks)-阿里云帮助中心

DataWorks has product-specific charge and overdue-payment behavior for pay-as-you-go products. This topic describes those charges and overdue payments.

Limits

Only pay-as-you-go products are subject to the DataWorks-specific charge and overdue-payment behavior described here.

Charges and overdue payments

Important

Alibaba Cloud offers a service suspension grace period. If a pay-as-you-go resource becomes overdue, you may continue using the cloud service within a certain credit amount or time period, and normal charges continue during the grace period. The grace credit is not a cap on your total overdue balance. Your credit amount or duration is calculated and updated each month based on factors such as your Alibaba Cloud spending history. For more information, see Service suspension protection for overdue payments.

The following table describes charges and overdue payments for pay-as-you-go products.

Billable item	Billing cycle	Charge details	Overdue-payment details
Serverless resource group (pay-as-you-go)	Daily	At the start of each day, a spending record for the previous day is generated from the CU usage. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Serverless resource group billing.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended. Instances that have not started cannot be started; instances already running can continue until they finish. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Number of scheduled instances	Daily	At the start of each day, a spending record for the previous day is generated from the number of instances that ran successfully. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Scheduling instance fees.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended. Instances that have not started cannot be started; instances already running can continue until they finish. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Public DataService resource group	Hourly	At the start of each hour, a spending record for the previous hour is generated from its usage. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Public DataService resource group billing.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended and published APIs can no longer be called normally. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Public network traffic for Data Integration	Hourly	At the start of each hour, a spending record for the previous hour is generated from its usage. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Public network traffic billing.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended. Instances that have not started cannot be started; instances already running can continue until they finish. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Data Quality instances	Daily	At the start of each day, a spending record for the previous day is generated from the number of instances that ran successfully. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Billing for data quality instances. Note A rule counts as successfully run when the rule itself executes successfully. Alerts or blocks caused by data quality problems are also billed as successful runs. After 160,000 Data Quality rule instances run in a day, the pay-as-you-go limit is reached and subsequent rule instances stop running. To request a higher daily instance limit, submit a ticket for assistance.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended. New Data Quality rule instances cannot be started; instances already started are unaffected. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Intelligent Baseline instances	Daily	At the start of each day, a spending record for the previous day is generated from the number of enabled baseline instances. The corresponding balance is frozen during the month, and the actual amount is deducted after the final bill is generated at the start of the next month. For rates, see Billing for intelligent baseline instances. Note An hourly baseline for an hourly task is billed as one baseline instance. If more than 100 baselines are enabled, the pay-as-you-go limit is reached and no more baseline instances can be generated. To request a higher baseline instance limit, submit a ticket for assistance.	The account is overdue for less than 24 hours Service continues for 24 hours. Notifications are sent at 12 and 23 hours after the account becomes overdue to remind you to add funds. The account has been overdue for more than 24 hours The service is suspended. New baseline instances cannot be generated; instances already started are unaffected. After adding funds If you add funds within 24 hours of becoming overdue, the service is not suspended.
Alert SMS messages and calls	Daily	Not applicable	Not applicable
OpenAPI calls	Daily	Not applicable	If your account is overdue, the service stops immediately. To avoid disruption, add funds promptly.

Limits

Charges and overdue payments

Related reading