Auto triggered tasks depend on resource groups to run. Tasks are categorized as scheduling tasks or compute-optimized tasks based on whether they consume compute units (CUs) from a resource group. Scheduling tasks are only triggered and monitored by DataWorks and do not consume compute resources from the resource group. Compute-optimized tasks have their code executed by DataWorks and consume compute resources. Configuring resource properties for tasks in the scheduling configuration ensures stable operation and helps optimize costs.
Core concepts
All auto triggered tasks in DataWorks must run on a resource group. Tasks are divided into two types based on whether they consume DataWorks CUs during execution:
Task type | Core responsibility | CU consumption | Task list |
Scheduling task | Only triggers and monitors computations in external compute engines, such as MaxCompute and Hologres. | None | |
Compute-optimized task | Task code is executed directly within a DataWorks resource group to perform computations. | Usage |
This topic focuses on CU configurations for
Serverlessresource groups. If you use exclusive or subscription resource groups, you do not need to configure CUs. You only need to specify the resource group.This topic does not cover the resource consumption or billing of third-party engines, such as MaxCompute, that are called by tasks.
Configuration steps
All auto triggered tasks must have schedule resources configured. The configuration process varies slightly depending on the task type and resource group type.
Step 1: Specify the scheduling resource group (required for all tasks)
This is a basic configuration step for all auto triggered tasks.
In the task code editor, find the Scheduling Configuration pane on the right.
In the Resource Properties section, select a resource group for scheduling from the drop-down list.
ImportantWhen you select a resource group, ensure that it can connect to the data sources and compute resources that the task accesses. Otherwise, the task may fail to run. For more information about network connectivity, see Network connection configurations.
Step 2: Configure compute resources (for compute-optimized tasks only)
If your task is a compute-optimized task and you selected a Serverless resource group in Step 1, you must also configure this item.
Tip: You can skip this step if you are using a scheduling task or a non-Serverless resource group.
The Scheduling CUs configuration item is automatically displayed under the Scheduling Resource Group.
Set the number of CUs required at runtime based on the task's complexity and performance requirements, such as 0.25 CU, 1 CU, or 4 CUs. A proper CU configuration ensures stable task execution and helps optimize costs.
Step 3: Configure an image
For PyODPS and Shell tasks, you can also configure an Image to define the runtime environment. For more information about image management, see Custom images.
Set the default scheduling resource group
When you create a task, the scheduling resource group specified in the Scheduling Settings is used as the default scheduling property. To change this default, click the 
icon in the lower-left corner and go to to modify the default scheduling resource group.
Billing description
Using a Serverless resource group to run auto triggered tasks involves the following two types of fees:
Task scheduling fees: These fees are generated by DataWorks based on the number of successfully run instances per day. For more information, see Task scheduling billing.
Resource usage fees: These fees are incurred only when compute-optimized tasks run on a pay-as-you-go Serverless resource group. Billing is based on the CUs consumed and the runtime duration. These fees do not include charges for third-party engines called by the task. For more information, see Serverless resource group billing.
The resource consumption of data integration tasks is not determined by the Scheduling CUs configuration. Instead, it is determined by the CUs to Occupy setting that you specify when you configure the resource group for the task.