The task orchestration feature of Data Management (DMS) allows you to configure a dependency check node for a task flow. You can specify whether a task flow depends on a node in the same task flow or on another task flow. This topic describes how to configure a dependency check node for a task flow.
Scenarios
- Inter-task flow dependency: Task Flow A runs only after Task Flow B succeeds.
For example, Task Flow A runs at 2:00 every Monday to train a recommendation model. Task Flow A runs on top of the business data of the last week (Monday to Sunday) that is generated by Task Flow B. Hence, Task Flow A is dependent on Task Flow B.
- Self-dependency: Task Flow A runs only after its previous cycle is complete.
For example, Task Flow A performs data cleansing. It can run only after the previous instance of Task Flow A is complete.
Usage notes
- Manually triggered task flows: Select a descendant node of the dependency check node for the task flow, and click Test Run Current Node or Start Test Run from Current Node. The dependency check node for the task flow is skipped, and a record indicating that the test run is successful is generated.
- Auto triggered task flows: On the task flow details page, click the
icon, and select Dry Run.
Note Then a successful auto triggering record is generated. (The task flow is not run.) - If a node depends on multiple nodes, you must configure the dependency of the node on other nodes separately. For example, if Node D depends on Nodes A, B, and C, you must configure the dependency of Node D on each of these nodes. The following steps show how to configure the dependency.