Configure node scheduling in DataWorks-DataWorks(DataWorks)-阿里云帮助中心

Prerequisites

A node has been created. Select a node type based on your business requirements. Data development process.
Periodic scheduling is enabled for the workspace. A node can be scheduled automatically only after this is enabled. Enable it on the Scheduling Settings page. Configure scheduling settings.

Important

Scheduling configuration takes effect only after the node is deployed to the production environment.
The scheduled time is the expected run time. Actual run time depends on upstream node completion. Run diagnostics.
For complex dependency scenarios, read Must read: Principles and examples for scheduling configurations in complex dependency scenarios to understand preset dependency behavior.
A scheduled task generates instances based on its scheduling type and cycle count. For example, an hourly task generates one instance per hour each day, and these instances run automatically.
If you use scheduling parameters, runtime values for each cycle are determined by the scheduled time and your parameter expressions. Supported formats for scheduling parameters.

Access the scheduling configuration

Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
Go to the scheduling configuration page.
1. In DataStudio, find the target node and go to the node editing page.
2. In the right-side navigation pane of the node editing page, click Properties to open the node scheduling configuration page.

Node scheduling properties

The following scheduling properties are available for each node.

Parameter	Description
General	Basic node information: name, ID, type, and owner. Node ID: Generated after the node is committed. Owner: Defaults to the node creator. You can reassign to another workspace member.
(Optional) Scheduling parameters	Define parameters for scheduled runs. DataWorks supports built-in and custom parameters for dynamic value assignment. Note If you define a variable in the node code, you must assign its value here.
Schedule	Configure how the task runs periodically in the production environment. Instance Generation Mode: Determines when the system generates an instance for the task. Recurrence: The run status of the task in the production environment. Scheduling Calendar: Scheduling dates and methods. DataWorks provides default calendars, or you can create a custom one. Configure a scheduling calendar. Scheduling Cycle: The frequency at which the task runs. Scheduled Time: The expected run time of the task. Timeout Definition: Maximum allowed run time before the task is automatically terminated. Rerun: Whether a failed instance can be rerun. Auto Rerun upon Failure: If rerun is enabled, the frequency at which the system automatically retries after a failure. Validity Period: The time range during which the task is scheduled. No instances are generated outside this period.
Resource properties	Specify the scheduling resource group for the task in the production environment.
Dependencies	Define upstream and downstream dependencies to ensure nodes run in the correct order. A downstream node runs only after all its upstream nodes succeed. Use automatic parsing for quick setup or configure dependencies manually. If a node is the first in a workflow or has no dependencies, set it to depend on the workspace root node for quick deployment. For workflows with multiple input/output nodes or complex dependencies, use a zero load node to manage the workflow, such as controlling its overall scheduling time. Note For nodes in the same workflow, you can also set dependencies by drawing lines between them in the workflow panel. Each workspace has an auto-generated root node (a zero load node) that serves as the default starting point for scheduling workflows. The node is named in the format `Workspace name_root`. The node is scheduled to run at `00:00` on the day after the workspace is created. The node performs a dry run — the system returns a success status without executing a task. No scheduling resources are consumed and no fees are incurred. Zero load node. Dry run.
(Optional) Input and output parameters	Define how parameters pass between upstream and downstream nodes. A downstream node can reference an output parameter defined in an upstream node.

Next steps

After configuring scheduling, commit the node and debug it to verify the configuration. Then deploy the node to the production environment for periodic scheduling. Perform basic O&M operations on scheduled tasks.