An auto triggered node instance is a snapshot that is taken for an auto triggered node at the time the node is scheduled to run. You can view the details of and perform the required operations on an auto triggered node instance in the list of auto triggered node instances. You can also view the details of and perform the required operations on an auto triggered node instance in the directed acyclic graph (DAG) of the instance.

An instance is generated each time an auto triggered node is run as scheduled. You can manage auto triggered node instances that have been scheduled. For example, you can view the running status of instances, and stop, rerun, and unfreeze instances.
Note
  • Instances are generated as scheduled for auto triggered nodes. Each generated instance runs the latest code. If you modify and recommit the node code after instances are generated for the node, the instances that have not been run will run the latest code.
  • If no alert is generated for a failed instance, you must check whether your mobile number and email address are configured on the Personal Account page.

Limits

DAGs have the following limits:
  • Only users of the DataWorks Standard Edition or a more advanced edition can use the node aggregation, upstream analysis, and downstream analysis features provided by DAGs.
  • Users of the DataWorks Basic Edition or Standard Edition can use the node aggregation, upstream analysis, and downstream analysis features provided by DAGs on a trial basis free of charge as of May 31, 2021. From June 1, 2021, users must update their DataWorks to the Professional Edition before they can use these features. For more information about DataWorks editions, see DataWorks advanced editions.
  • You can use the node aggregation, upstream analysis, and downstream analysis features of the DAGs of auto triggered nodes that are deployed only in the China (Shenzhen) region.

Manage auto triggered node instances

You can manage auto triggered node instances in the instance list. For example, you can check operational logs, rerun instances, and stop running instances. Auto triggered node instances
Operation Description
Filter You can specify filter conditions to search for your desired instance in the section marked with 1 in the preceding figure.

You can search for instances by node name or node ID. You can also specify the following conditions to search for your desired instance: Data Timestamp, Node Type, Run At, Solution, Workflow, Region, Engine Type, Engine Instance, Baseline, Owner, Scheduling Type, Status, My Nodes, My Nodes with Errors, and My Incomplete Nodes.

Note By default, the data timestamp is set to the previous day of the current day.
Stop Allows you to stop the instance. You can stop an instance only when it is in the Pending (Schedule), Pending (Resources), or Running state. After this operation is performed, the instance enters the Failed state.
Rerun Allows you to rerun the instance. After the instance is rerun, its pending descendant instances are run as scheduled. Perform this operation if an instance fails to be run or it is not run as scheduled.
Note Only instances in the Successful or Failed state can be rerun.
Rerun Descendent Nodes Allows you to rerun the instance and its descendant instances. You must specify the instances that you want to rerun. After they are run, their pending descendant instances are run as scheduled. Perform this operation to recover data.
Note Only instances in the Pending (Ancestor), Successful, or Failed state can be selected. The value No appears in the Meet Rerun Condition column of instances in other states, and you cannot select the instances.
Set Status to Successful Allows you to set the status of the instance to Successful and run its pending descendant instances. Perform this operation if an instance fails to be run.
Note Only the status of a failed instance can be set to Successful. This operation does not apply to workflows.
Freeze Allows you to freeze the instance that is in the Running state.
Unfreeze Allows you to unfreeze the instance that is frozen.
  • If the instance is not run, it is automatically run after the running of its ancestor instances is complete.
  • If all the ancestor instances are run, the status of the instance is directly set to Failed. You must manually rerun the instance.
Batch operations Allows you to perform batch operations. You can click the following buttons to perform batch operations on instances: Stop, Rerun, Set Status to Successful, Freeze, and Unfreeze.

Manage auto triggered node instances in a DAG

Click DAG in the Actions column that corresponds to a node to view the DAG of the node. You can perform the following operations in a DAG: DAG features
  • Aggregate nodes
    If an auto triggered node has multiple ancestor and descendant nodes or the ancestor and descendant nodes are distributed at multiple levels, you can aggregate the nodes. The nodes can be aggregated from dimensions such as node status, workspace, owner, and priority. Then, you can view the number of nodes from your required dimension. This allows you to understand the number of nodes from different dimensions and helps the system run the nodes. The following figures show the node distribution when the ancestor and descendant nodes of an auto triggered node are not aggregated or are aggregated by priority.
    • The following figure shows the node distribution when the ancestor and descendant nodes of an auto triggered node are not aggregated. Ancestor and descendant nodes of an auto triggered node not aggregated
    • The following figure shows the node distribution when the ancestor and descendant nodes of an auto triggered node are aggregated by priority. From the figure, you can quickly understand that the current auto triggered node has six descendant nodes whose priorities are 1. Ancestor and descendant nodes of an auto triggered node aggregated by priority
  • Analyze ancestor nodes
    In most cases, an auto triggered node has both upstream and downstream relationships. If an auto triggered node is not run for a long time, you can analyze the ancestor nodes of the node. You can view the ancestor node that blocks the running of the node in the DAG of the node, and quickly locate and troubleshoot the issue. This improves the running efficiency of the node.
    Note You can analyze the ancestor nodes of only the auto triggered nodes that are not run.
    The following figure shows how to analyze the ancestor nodes of an auto triggered node. For example, the 2_ node is not run for a long time. In this case, you can click the node and click Upstream Analysis in the upper-left corner to analyze the ancestor nodes of the node. An auto triggered node is not runThe analysis results show that the ancestor nodes that block the running of the 2_ node are the table data synchronization and metric statistics nodes. Then, you can quickly troubleshoot the issue based on the analysis results.
  • Analyze descendant nodes
    If an auto triggered node has multiple descendant nodes or the descendant nodes of an auto triggered node are distributed at multiple levels, you can analyze the descendant nodes of the auto triggered node. You can aggregate the descendant nodes by node status, workspace, owner, or priority. Then, you can view the number of nodes at different levels from your required dimension or the total number of nodes at all levels from your required dimension.
    Note
    • By default, the descendant nodes of an auto triggered node are aggregated by owner. The system calculates the total number of nodes at all levels from the owner dimension.
    • If you analyze the descendant nodes of an auto triggered node, the analysis results are displayed by level, and a maximum of six levels of nodes can be displayed. If you want to view more levels of nodes, click Continue Analysis in the upper-left corner.
    In the following example, the descendant nodes of the tag node are analyzed. The following figures show the analysis results that are displayed by using different methods.
    • The descendant nodes of the tag node are aggregated based on the workspaces to which the descendant nodes belong, and the analysis results are presented by level. This way, the number of the descendant nodes in different workspaces is displayed at different levels. Analysis results displayed by level
    • The descendant nodes of the tag node are aggregated based on the workspaces to which the descendant nodes belong, and the analysis results are presented by using the merging method. This way, all the descendant nodes are placed at the same level, and the number of the descendant nodes that belong to different workspaces is displayed. Analysis results displayed by using the merging method
  • Select a display pattern for a DAG

    You can click the icons in the upper-right corner of a DAG panel to adjust the display pattern of the DAG based on your business requirements. For example, you can click Toggle Full Screen View or Fit Screen to perform the operation.

    In the following examples, the DAG of the 0_2 node is displayed after the descendant nodes of the 0_2 node are ungrouped or grouped:
    • The following figure shows the DAG of the 0_2 node when the descendant nodes of the 0_2 node are ungrouped. In this pattern, you can clearly view the upstream and downstream relationships of all the nodes. DAG of the 0_2 node when the descendant nodes of the 0_2 node are ungrouped
    • The following figure shows the DAG of the 0_2 node when the descendant nodes of the 0_2 node are grouped. In this pattern, every five descendant nodes of the 0_2 node are placed at the same level. This way, these descendant nodes are displayed in an orderly manner, and you can quickly obtain the total number of the descendant nodes. DAG of the 0_2 node when the descendant nodes of the 0_2 node are grouped
  • Right-click your desired node in a DAG and perform operations on the node. DAG
    Operation Description
    Show Ancestor Nodes or Show Descendent Nodes If a workflow contains three or more nodes, specific nodes are automatically hidden in the DAG in Operation Center. You can select the number of levels to view all nodes at one or more levels.
    View Runtime Log Allows you to view the operational logs of the current instance that is in the states such as Running, Successful, or Failed.
    Instance Diagnose DataWorks Operation Center provides the instance diagnosis feature to help you track the running of nodes and identify problems. For more information, see Instance diagnosis.
    View Code Allows you to view the code of the current instance.
    Edit Node Allows you to go to the DataStudio page and modify the current node.
    View Lineage Allows you to view the lineage of the current instance.
    More Allows you to view more instance information on the General, Context, Runtime Log, Operation Log, and Code tabs.
    Stop Allows you to stop the instance. Only instances in the Pending or Running state can be stopped. After this operation is performed, the instance enters the Failed state.
    Rerun Allows you to rerun the instance. After the instance is rerun, its pending descendant instances are run as scheduled. Perform this operation if an instance fails to be run or it is not run as scheduled.
    Note Only instances in the Pending (Ancestor), Successful, or Failed state can be rerun.
    Rerun Descendent Nodes Allows you to rerun the instance and its descendant instances. You must specify the instances that you want to rerun. After they are run, their pending descendant instances are run as scheduled. Perform this operation to recover data.
    Note Only instances in the Pending (Ancestor), Successful, or Failed state can be selected. The value No appears in the Meet Rerun Condition column of instances in other states, and you cannot select these instances.
    Set Status to Successful Allows you to set the status of the instance to Successful and run its pending descendant instances. Perform this operation if an instance fails to be run.
    Note Only the status of a failed instance can be set to Successful. This operation does not apply to workflows.
    Resume Allows you to continue to run the instance after it fails.
    Emergency Operations Allows you to perform emergency operations in emergencies only. Emergency operations take effect only once on the current node.

    Select Delete Dependencies to delete the dependencies of the current node. You can perform this operation to start the current node if the ancestor instances fail and the current instance does not depend on the data of the ancestor instances.

    Freeze Allows you to freeze the instance that is in the Running state.
    Unfreeze Allows you to unfreeze the instance that is frozen.
    • If the instance is not run, it is automatically run after the running of its ancestor instances is complete.
    • If all the ancestor instances are run, the status of the instance is directly set to Failed. You must manually rerun the instance.

Instance states

No. State Icon
1 Run successfully 1
2 Not running 2
3 Run failed 3
4 Running 4
5 Waiting time 5
6 Freeze 6