Data Management:Configure a dependency check node for a task flow

Use cases

• Inter-task flow dependency: Task Flow A runs only after Task Flow B completes successfully. For example, Task Flow A runs at 02:00 every Monday to train a recommendation model. It depends on the previous week's business data (Monday through Sunday) generated by Task Flow B, so Task Flow A must not start until Task Flow B finishes.

• Self-dependency: Task Flow A runs only after its previous cycle finishes. For example, a data cleansing task flow must complete its current run before the next scheduled run can start.

Usage notes

• A new task flow must have at least one completed node before it can be set as a dependency target.

• If a node depends on multiple upstream nodes, configure each dependency separately. For example, if Node D depends on Nodes A, B, and C, add three separate dependency check configurations — one for each upstream node.

• To generate a completed record before the dependency is active:

  • Manually triggered task flows: Select a descendant node of the dependency check node, then click Test run current node or Start test run from current. The dependency check node is skipped, and a successful test run record is generated.

  • Auto triggered task flows: On the task flow details page, click the icon and select Dry Run.

  Dry Run generates a successful auto-triggering record without actually running the task flow.

Prerequisites

Before you begin, ensure that you have:

• Access to the DMS console V5.0

• An existing task flow. For instructions, see Overview

• At least one completed node in the task flow you want to set as a dependency

Add a dependency check node

1. Log on to the DMS console V5.0.

2. In the top navigation bar, choose Data+AI > Data+AI > Task Orchestration.

   In simple mode, move the pointer over the icon in the upper-left corner and choose All Features > Data+AI > Data Development > Task Orchestration.

3. Click the name of the task flow to open its details page.

4. From the Task Type list on the left side of the canvas, drag the Check for Task Flow Dependency node onto the canvas.

5. Double-click the Check for Task Flow Dependency node to open its configuration page.

6. Configure the following parameters.

   Parameter	Description
   Task Flow	The task flow to depend on. Search for and select a task flow in the Task Flow field. If you select the current task flow, it depends on its own previous cycle (self-dependency). If you select a different task flow, it depends on that task flow's result.
   Dependency Object	The type of dependency target. Task Flow — depends on an entire task flow. Single Node — depends on a specific node within a task flow.
   Dependency Settings	The time window for the dependency check, defined by Start Time Offset and End Time Offset. Offsets are calculated from the task's execution time by default. For auto triggered task flows, the business time is the scheduled execution time. For manually triggered task flows, the business time is the time the task flow was manually triggered. See Dependency settings examples for details.
   Check Policy for Database Instances	When the dependency check passes. Last Round Succeeded — passes after the most recent run of the upstream node succeeds. All Round Succeeded — passes only after all runs of the upstream node succeed. Specified Round Succeeded — passes after a specific run of the upstream node succeeds. For manually triggered task flows, only manually triggered nodes are checked; for auto triggered task flows, only auto triggered nodes are checked. For example, if Task Flow A has only been manually triggered and never auto triggered, a dependency check test run succeeds, but Task Flow A fails to auto trigger.
   Check Type	How the time offsets are calculated. Run At — offsets are based on the actual task execution time. Business Date — offsets are based on the bizdate variable, which represents the day before the task execution time.

7. Click Try Run to validate the configuration.

   • If status SUCCEEDED appears in the last line of the execution log, the configuration is valid.

   • If status FAILED appears, review the execution log to identify which node failed and why. Update the configuration and try again.