Auto triggered nodes are automatically run as scheduled after being committed to the scheduling system.
- By default, the auto triggered node list displays nodes in all the workflows created by the current Alibaba Cloud account.
- After you commit a node, the scheduling system automatically generates and runs an instance of the node at 23:30 the next day. If you commit a node after 23:30, the scheduling system generates and runs an instance of the node on the third day.
- 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, auto triggered node instances cannot be run.
Manage auto triggered nodes in the node list
The Cycle Task page displays auto triggered nodes that are committed to the scheduling system in a list.
|Filter||Find required nodes by setting parameters in the red box marked with 1 in the preceding
You can search for nodes by node name or node ID and set Solution, Workflow, Node Type, Owner, Region, Engine type, Engine instance, Baseline, My Nodes, Modified Today, and Frozen to filter nodes.
Note When you search for nodes by node name, the search result is affected by other filtering conditions. Only nodes that meet both the specified search condition and other filtering conditions are returned in the search result.
|DAG||Click DAG in the Actions column to view the directed acyclic graph (DAG) of the node. You can view the node information, such as properties, operational logs, and code, in the DAG.|
|Test||Click Test in the Actions column to test the node. For more information, see Test instances.|
|Patch Data||Click Patch Data in the Actions column to generate retroactive data for the node. For more information, see Retroactive instances.|
|More||Click More in the Actions column to perform more operations, such as freezing the node, unfreezing
the node, and viewing instances of the node.
|Batch operations||Select multiple nodes and click a button in the red box marked with 3 in the preceding figure to perform batch operations. The buttons include Configure Alert Trigger, Change Owner, Change Resource Group, Add to Baseline, Freeze, Unfreeze, and Delete.|
Manage auto triggered nodes in a DAG
Click the name of a node or DAG in the Actions column to view the DAG of the node. In the DAG, you can right-click the node to perform related operations.
|Show Ancestor Nodes and Show Descendant Nodes||Show ancestor or descendant nodes 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.|
|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 Smoke Test Instance Name and Data Timestamp and click OK. Then, the Test Instance page appears.|
|Run||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.|
Right-click a node with advanced settings. The Expand Ancestor Nodes Across Regions menu appears. For more information about advanced settings, see Advanced configuration.
You can select Expand Ancestor Nodes Across Regions to view the name of the node in another region on which the current node depends and the nodes for pushing and checking messages. Currently, DataWorks cannot generate retroactive data for a node with an ancestor node in another region or test such a node.