An auto triggered node instance is a snapshot of an auto triggered node that is taken when the node is scheduled to run at a specified point in time.

An instance is generated each time an auto triggered node is run as scheduled. You can manage auto triggered node instances that have been run. 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, the instances that have not been run will run the latest code.
  • If no alert is generated for a failed instance, check whether your mobile number and email address are configured on the Personal Account page.

Auto triggered node instance list

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 Find required instances by setting filter conditions in the section marked with 1 in the preceding figure.

You can search for instances by node name or node ID and set the following parameters to filter instances: Data Timestamp, Node Type, Run At, Solution, Workflow, Region, Engine type, Engine instance, Baseline, Owner, Recurrence, 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 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 Rerun the instance. After the instance is rerun, its pending descendant instances are run as scheduled. Perform this operation if an instance fails or it is not run as scheduled.
Note Only instances in the Successful or Failed state can be rerun.
Rerun Descendent Nodes Rerun the instance and its descendant instances. You must specify the instances 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 Set the status of the instance to Successful and run its pending descendant instances. Perform this operation if an instance fails.
Note Only the status of a failed instance can be set to Successful. This operation does not apply to workflows.
Freeze Freeze the instance if it is in the Running state.
Unfreeze Unfreeze the instance after it is frozen.
  • If the instance is not run, this instance is run automatically after its ancestor instances are run.
  • 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 Click a button in the section marked with 3 in the preceding figure to perform batch operations. The buttons include Stop, Rerun, Set Status to Successful, Freeze, and Unfreeze.

Instance DAG

Click the name of an instance or DAG in the Actions column to view the directed acyclic graph (DAG) of the instance. In the DAG, you can right-click the instance to perform related operations.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 Allow you to view the operational logs of the current instance if it is in the Running, Successful, or Failed state.
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 Allow you to view the code of the current instance.
Edit Node Click this menu item to go to the DataStudio page and modify the current node.
View Lineage Allow you to view the lineage of the current instance.
More Click More to view more instance information on the General, Context, Runtime Log, Operation Log, and Code tabs.
Stop Only instances in the Pending or Running state can be stopped. After this operation is performed, the instance enters the Failed state.
Rerun Rerun the instance. After the instance is rerun, its pending descendant instances are run as scheduled. Perform this operation if an instance fails or it is not run as scheduled.
Note Only instances in the Pending (Ancestor), Successful, or Failed state can be rerun.
Rerun Descendent Nodes Rerun the instance and its descendant instances. You must specify the instances 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 Set the status of the instance to Successful and run its pending descendant instances. Perform this operation if an instance fails.
Note Only the status of a failed instance can be set to Successful. This operation does not apply to workflows.
Resume Continue to run the instance after it fails.
Emergency Operations Perform emergency operations in emergency only. Emergency operations take effect only on the current instance for one time.

Select Delete Dependencies to delete the dependencies of the current node. Perform this operation so that you can start the current node when the ancestor instances fail and the current instance does not depend on the data of the ancestor instances.

Freeze Freeze the instance if it is in the Running state.
Unfreeze Unfreeze the instance after it is frozen.
  • If the instance is not run, this instance is run automatically after its ancestor instances are run.
  • 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 Successful 1
2 Pending (Ancestor) 2
3 Failed 3
4 Running 4
5 Pending (Schedule) 5
6 Freeze 6