All Products
Search

This Product

    DataWorks:Create and use a zero load node

    Document Center

    DataWorks:Create and use a zero load node

    Last Updated:Aug 21, 2026

    A zero-load node is a control node that performs dry-run scheduling without generating data or consuming resources. When its scheduled time arrives, the system immediately returns a success response, allowing descendant nodes to run as expected. Zero-load nodes typically serve as the start node of a workflow or as an aggregation point for multiple branch nodes.

    Scenarios

    Common scenarios for zero-load nodes:

    • Manage workflows in scenarios in which dependencies between nodes are complex

      If you manage multiple workflows, use a zero-load node as the orchestration start node for each workflow.业务管理

    • Schedule nodes that have no lineage relationship

      For a workflow with multiple independent input branches, use a zero-load node as their common parent node and set the workspace root node as its parent. The workspace root then triggers the zero-load node, which in turn triggers the downstream business nodes. You can also set a specific schedule on the zero-load node to control the earliest start time for all downstream branches.

      Note

      When the workspace root node is set as a dependency, it does not appear on the workflow canvas. You can view it in Operation Center after task deployment. For more information, see Basic O&M for scheduled tasks.

      For example:调度无血缘依赖节点 The oss_data_sync_dqc and rds_data_sync_dqc nodes have no lineage, so scheduling dependencies cannot be configured between them based on lineage. Instead, use a zero-load node such as workshop_start_dqc as an orchestration start node to schedule these independent downstream branches. The branches run as soon as their respective conditions are met.

      Note

      When you use offline synchronization to import data from other sources into DataWorks, the destination tables lack an upstream lineage within DataWorks.

    • Configure scheduling dependencies for branch nodes in a workflow on nodes in another workflow

      To make a workflow dependent on multiple branches in another workflow, use a zero-load node to aggregate the outputs from those branches. Then, manually set this aggregation node's output as an input for the orchestration start node of the downstream workflow. For more information, see Configure a cross-workflow scheduling dependency.

      Note

      If a workflow has multiple output branches, create a zero-load node (for example, a workflow_end node) that depends on all of them. When this node runs successfully, it indicates that the entire workflow has completed.

    Create and use a zero load node

    1. Go to the DataStudio page.

      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.

    2. Create a Workflow.

      If you have an existing Workflow, skip this step.

      1. Hover over the 新建 icon and select Create Workflow.

      2. In the Create Workflow dialog box, enter a Workflow Name.

      3. Click Create.

    3. Create a zero load node.

      1. Hover over the image.png icon and select Create Node > General > Zero-Load Node.

        Alternatively, find the target workflow, right-click it, and select Create Node > General > Zero-Load Node.

      2. In the Create Node dialog box, enter a Name and select a Node Type and Path.

        Note

        The node name can contain only uppercase and lowercase letters, Chinese characters, digits, underscores (_), and periods (.). The name cannot exceed 128 characters.

      3. Click OK to open the configuration tab for the zero-load node.

    4. Configure scheduling properties for the zero load node.

      To run the node periodically, click Scheduling Settings on the right of the node's configuration tab, then configure the scheduling properties:

    5. Commit and deploy the task.

      1. In the toolbar, click the 保存 icon to save the node.

      2. In the toolbar, click the 提交 icon to commit the task.

      3. In the Commit Node dialog box, enter a Change Description.

      4. Click Determine.

      In a standard mode workspace, you must deploy the task to the production environment after you commit it. In the top menu bar, click Deploy. For more information, see Deploy tasks.

    6. View scheduled tasks.

      1. In the upper-right corner of the editor, click O&M Personnel to open the production environment's Operation Center.

      2. View the scheduled tasks that are running. For more information, see Manage scheduled tasks.

      To view more details about scheduled tasks, click Operation Center in the top menu bar. For more information, see Operation Center overview.