The task orchestration feature of Data Management (DMS) allows you to configure a task flow dependency check node. After you configure the node, the task flow depends on the result of its previous cycle or another task flow. You can specify the task flow to depend on another task flow or a node. This topic describes how to configure a task flow dependency check node.

Scenarios

  • Cross-task flow dependency: Task Flow A can run only after Task Flow B is run as expected.

    For example, Task Flow A is run at 2:00 every Monday to train a recommendation model. Task Flow A depends on the business data generated by Task Flow B from last Monday to Sunday.

  • Self-dependency: Task Flow A can run only after its previous cycle is complete.

    For example, Task Flow A that performs data cleansing can be run only after the data cleansing of its last cycle is complete.

Procedure

  1. Go to the DMS console V5.0.
  2. In the top navigation bar, click DTS. In the left-side navigation pane, choose Data Development > Task Orchestration.
  3. Click the name of the task flow that you want to manage to go to the details page of the task flow.
    Note For more information about how to create a task flow, see Overview.
  4. In the Task Type list on the left side of the canvas, drag the task flow dependency check node to the blank area on the canvas.
  5. Double-click the task flow dependency check node.
  6. On the configuration page of the task flow dependency check node, set the parameters described in the following table as needed.
    Parameter Description
    Task Flow The task flow for which you want to configure a task flow dependency check node. You can search for and select the specified task flow in the Task Flow field.
    Note
    • If you select the current task flow, the task flow depends on the result of its previous cycle.
    • If you select another task flow, the current task flow depends on the result of the selected task flow.
    Dependency Object The type of the dependency object. Valid values:
    • Task Flow: The current task flow depends on another task flow.
    • Single Node: The current task flow depends on a specific node.
    Dependency Settings The time settings of the task flow dependency check. The settings include the start time offset and the end time offset.
    Check Policy for Database Instances
    • Last Round Succeeded: The task flow passes the task flow dependency check only if the last node is run as expected.
    • All Round Succeeded: The task flow passes the task flow dependency check only if all nodes are run as expected.
    • Specific Round Succeeded: The task flow passes the task flow dependency check only if the task flow is successfully run at the specified cycle.
    Note
    • For a manually triggered task flow, only manually triggered nodes are checked.
    • For an auto triggered task flow, only the auto triggered nodes are checked.
    For example, Task Flow A has been manually triggered but not automatically triggered. If you perform a task flow dependency check for Task Flow A, the test run can succeed but the task flow may fail to be automatically triggered.
  7. Click Try Run.
    • If status SUCCEEDED appears in the last line of the logs, the test run is successful.
    • If status FAILED appears in the last line of the logs, the test run fails.
      Note If the task flow fails to be run, view the node on which the failure occurs and the reason for the failure in the logs. Then, modify the configuration of the node and try again.

Usage notes

For a new task flow that depends on the result of its previous cycle, you must make sure that at least one node has been run as expected.
  • Manually triggered task flows: Right-click a descendant node of the task flow dependency check node and click Test run current node or Start test run from current to skip the task flow dependency check node and generate a record for the node that is run as expected.
  • Auto triggered task flows: Click the Try Run drop-down list icon next to Try Run and select Dry Run. After that, a record is generated for the auto triggered task flow that is dry run.