Configure resource properties for scheduled tasks-DataWorks(DataWorks)-阿里云帮助中心

Scheduled tasks run on resource groups. Tasks that only trigger and monitor external engines are scheduling tasks and consume no CUs, while tasks whose code runs inside DataWorks are compute tasks and consume CUs. Configure resource properties in scheduling configuration to ensure stable execution and optimize costs.

Key concepts

DataWorks classifies tasks into two types based on whether they consume Compute Units (CUs):

Task type	Core responsibility	CU consumption	Task list
scheduling task	Triggers and monitors computations in external compute engines, such as MaxCompute and Hologres.	Does not consume	List of scheduling tasks
compute task	Executes code directly within a DataWorks resource group to perform computations.	Consumes	List of compute tasks

Important

This topic covers CU configurations for Serverless resource groups. If you use dedicated or subscription resource groups, you only need to specify the resource group without configuring CUs.
This topic does not cover the resource consumption or billing of third-party engines called by tasks, such as MaxCompute.

Procedure

All scheduled tasks require resource configuration. The process varies by task type and resource group type.

Step 1: Specify a scheduling resource group

This baseline configuration applies to all scheduled tasks.

In the task editor, find the Scheduling Settings panel on the right.
In the Resource Group section, select a scheduling resource group from the drop-down list.

Important
Ensure the selected resource group can connect to the data sources and compute resources the task requires. Otherwise, the task might fail. For details, see Network Connectivity Configuration.

After you select a resource group, a message confirms that the current task is a scheduling task and does not require CUs.

Step 2: Configure compute resources (for compute tasks only)

If your task is a compute task and you selected a Serverless resource group in Step 1, complete this step.

Tip: You can skip this step for scheduling tasks or non-Serverless resource groups.

A CUs for Scheduling configuration option automatically appears below the Resource Group for Scheduling setting.
Set the CU count for runtime (for example, 0.25, 1, or 4 CUs) based on the task's compute complexity and performance needs. Proper CU allocation ensures stable execution and helps control costs.

Step 3: Configure an image

For task types such as PyODPS and Shell, you can define the runtime environment by configuring an Image. For details, see Custom Images.

The configuration form includes the following fields: scheduling resource group (required, for example, select dataworks_default_resource_group), scheduling CU (for example, enter 0.25), and image (select one from the drop-down list).

Set the default scheduling resource group

When you create a task, the scheduling resource group specified in Scheduling Settings is used as the default. To change it, click the PixPin_2025-12-09_15-59-34 icon in the lower-left corner, navigate to Configure > Scheduling Settings, and update the default resource group.

Billing

Running scheduled tasks on a Serverless resource group incurs two types of fees:

Task scheduling fees: Charged based on the number of successful task runs per day. For details, see Scheduling instance fees.
Resource usage fees: Apply only when a compute task runs on a pay-as-you-go Serverless resource group. Calculated based on the consumed CUs and the task's runtime. These fees do not include charges from third-party engines called by the task. For details, see Serverless resource group billing.

Note

For data integration tasks, resource consumption depends on the consumed CUs you specify for the resource group, not the scheduling CU setting.