Auto triggered nodes are automatically run as scheduled after they are committed to the scheduling system.

Background information

By default, the auto triggered node page displays nodes in all the workflows that are created by the current Alibaba Cloud account.
Notice Do not perform any operations on the Workspace name_root node, which is the root node of the workspace. All instances of auto triggered nodes depend on this node. If this node is frozen, instances of auto triggered nodes cannot be run.
Set the Start Instantiation parameter in the Schedule section. The following instance generation methods are supported:
  • Next Day:
    • If the node is committed and deployed before 23:30, instances are generated from the next day.
    • If the node is committed and deployed after 23:30, instances are generated from the day after the next day.
  • Immediately After Deployment: If the node is committed and deployed after 23:30, this method cannot be used. For more information, see Immediate instance generation.

Procedure

  1. Go to the DataStudio page.
    1. Log on to the DataWorks console.
    2. In the left-side navigation pane, click Workspaces.
    3. In the top navigation bar, select the region where your workspace resides, find the workspace, and then click Data Analytics in the Actions column.
  2. On the DataStudio page, click Auto triggered nodes in the upper-left corner and choose All Products > Operation Center.
  3. In the left-side navigation pane, choose Cycle Task Maintenance > Cycle Task.
  4. On the Cycle Task page, view the auto triggered node list or the directed acyclic graph (DAG) of nodes.
    The Cycle Task page displays auto triggered nodes that are committed to the scheduling system in a list or DAG.
    • Manage auto triggered nodes in the node list
      In the middle of the page, click the Right arrow icon to show the node list.Manage auto triggered nodes in the node list
      Action Description
      Filter Find required nodes by setting parameters in the red box marked with ① in the preceding figure.
      You can search for nodes by node name or node ID and set Solution, Workflow, Node Type, Owner, Region, Scheduling Resource Group, Engine type, Engine instance, Baseline, My Nodes, Modified Today, Frozen, Isolated node, and Expired node to filter nodes.
      Note When you search for nodes by node name, the search result is affected by other filter conditions you specified. Only nodes that meet both the specified search condition and other filter conditions are returned in the search result.
      DAG Click DAG in the Actions column of a node to view the DAG of the node. You can view the node information, such as properties, operations logs, and code, in the DAG.
      Test Click Test in the Actions column of a node to test the node. For more information, see Test instances.
      Patch Data Click Patch Data in the Actions column of a node to generate retroactive data for the node. For more information, see Retroactive instances.
      More Click More in the Actions column of a node to perform more operations on the node. You can perform the following operations on the node:
      • Select Freeze to freeze the node. After the node is frozen, DataWorks can still generate instances of the node, but does not run the instances of the node and its descendant instances.
      • Select Unfreeze to unfreeze the node. After the node is unfrozen, DataWorks can normally run the instances of the node and its descendant instances.
      • Select View Instances to view the instances of the node.
      • Select Configure Alert Trigger to configure alert triggers for the node.
      • Select Change Owner to change the owner of the node.
      • Select Add to Baseline to add the node to a baseline.
      • Select Modifying a scheduling Resource Group to change the resource group that is used to run the node. You can perform this operation if multiple resource groups exist in the workspace. In the Modifying a scheduling Resource Group dialog box, select a resource group from the New Resource Group drop-down list and click OK.
      • Select Configure Data Quality Rules to configure rules for monitoring the data quality of the node.
      • Select View Lineage to view the lineage of the node.
      • Select View Ancestor and Descendant Nodes to go to the Node Information page, where you can view node information on the Ancestor Nodes and Descendant Nodes tabs.
      Batch operations In the red box marked with ③ in the preceding figure, perform the following operations on the nodes in the node list: Change Owner, Modifying a scheduling Resource Group, Modify a data integration Resource Group, Freeze, Unfreeze, Configure Alert Trigger, Add to Baseline, and Delete.
    • Manage auto triggered nodes in a DAG
      Click DAG in the Actions column of a node to view the DAG of the node. In the DAG, you can right-click the node to perform related operations.DAG
      Action Description
      Show Ancestor Nodes View ancestor or descendant instances at one or more levels. If a workflow contains three or more nodes, the DAG only displays the current node and hides its ancestor and descendant nodes. Click to select the level numbers to view node dependencies. Select the largest number to view the most node dependencies.
      Show Descendant Nodes
      View Node Details Go to the Node Information page to view the node information, including the input table, output table, ancestor nodes, and descendant nodes.
      View Code View the code of the node.
      Edit Node Go to the DataStudio page to modify the node.
      View Instances View the instances of the node.
      View Lineage View the lineage of the node.
      Test Go to the Smoke Test dialog box. Set the Smoke Test Instance Name and Data Timestamp parameters and click OK. Then, the Test Instance page appears.
      Patch Data Select Current Node Retroactively, Current and Descendant Nodes Retroactively, or Mass Nodes Retroactively.
      Freeze Pause the scheduling of the node.
      Unfreeze Resume the scheduling of the node after it is frozen.
      Configure Data Quality Rules Configure rules for monitoring the data quality of the node.