DataWorks charges scheduling instance fees when you run scheduling tasks — such as data integration and data computing — using a Serverless resource group or a shared resource group for scheduling. Fees are calculated daily based on the number of instances that run successfully.
Resource group types
Both resource group types use the same tiered pricing model based on successful instances per day.
This topic covers only the scheduling instance fees generated by task scheduling. Serverless resource groups have separate subscription and pay-as-you-go billing methods. For more information, see Serverless resource group billing.
| Resource group type | Description | Billing method |
|---|---|---|
| Serverless resource group (Recommended) | Dedicated per tenant. Provides strong resource isolation and stable performance. | Tiered pricing based on successful instances per day (described in this topic). |
| Shared resource group for scheduling | Resources are shared across all tenants and apply only to scheduling tasks. Resource contention may occur during peak hours, which can prevent tasks from running on time. A limit applies to the total number of instances. | Same tiered pricing model. |
Billing scenarios
Scheduling instance fees apply when you use supported development nodes to run data integration tasks or compute-optimized tasks in the following scenarios:
Production environment (Operation Center):
-
Auto triggered tasks
-
Data backfill tasks
-
Test tasks
Developer environment (Operation Center):
-
Data backfill tasks
-
Test tasks
The Operation Center in the developer environment does not support auto triggered tasks.
Billing metrics
An instance is billable only if it meets both of the following conditions:
-
Submitted to the scheduling system — Instances generated by nodes submitted to the scheduling system are billable, except for instances generated by zero load nodes. This includes recurring, one-time, test, and data backfill instances.
-
Successfully run — Only instances that complete successfully in the Operation Center are billed.
What is not billed
The following instance states are not billed:
| State | Description |
|---|---|
| Not yet run | Instance was generated but has not been executed. |
| Failed | Instance attempted to run but did not complete successfully. |
| Frozen | Instance is in a frozen state. |
| Dry-run | Platform marks the instance as successful without executing the task. |
Example: An hourly task runs once per hour from 00:00 to 23:59 each day, generating 24 instances. If all 24 instances run successfully, the billable count for that day is 24.
Pricing
Billing unit: number of successful instances per day.
The shared resource group for scheduling has a usage limit. If the daily number of instances reaches or exceeds 120,000, instances may not run properly. For high-volume workloads, use a Serverless resource group to avoid this limitation.
DataWorks uses a 12-tier pricing model. The daily fee is determined by the tier that corresponds to your total successful instances for the day.
-
Billing cycle: Daily
-
Billing granularity: Number of successful instances per day
-
Free quota: The first 10 successful instances each day are free
China regions
Applies to: China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Chengdu), China (Hong Kong)
International regions
Applies to: Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), US (Silicon Valley), US (Virginia), Germany (Frankfurt), UK (London), UAE (Dubai), Thailand (Bangkok)
| Successful instances per day | Daily fee |
|---|---|
| 1–10 | Free |
| 11–500 | 0.23 USD |
| 501–5,000 | 13.93 USD |
| 5,001–20,000 | 34.82 USD |
| 20,001–50,000 | 62.68 USD |
| 50,001–120,000 | 139.30 USD |
| 120,001–300,000 | 306.46 USD |
| 300,001–700,000 | 696.50 USD |
| 700,001–1,500,000 | 1,462.65 USD |
| 1,500,001–3,200,000 | 3,111.03 USD |
| 3,200,001–7,000,000 | 6,500.67 USD |
| 7,000,001–14,000,000 | 12,885.25 USD |
View billing details
In the Expenses and Costs portal, look up your scheduling charges using these fields:
-
Billing Item:
Number of scheduled instances (Pay-As-You-Go) -
Billing Item Code:
dide_create_public_alisa_post
For details on navigating the billing portal, see View billing details.
FAQ
Why can't I calculate the cost of a single instance?
Scheduling uses tiered pricing: you pay a fixed daily fee based on which tier your total successful instances fall into, not a per-instance rate. Because the fee is tied to the daily total rather than individual instances, there is no per-instance cost, and bills cannot be queried at the individual instance level.
How do I estimate my scheduling instance count?
In the Operation Center, check the total number of instances across all four lists: recurring instance, data backfill instance, test instance, and one-time instance.