Auto triggered node instances are snapshots taken for auto triggered nodes that are run.

An instance is generated each time an auto triggered node is run as scheduled. You can manage auto triggered node instances. For example, you can view the running status of instances, and stop, rerun, or unfreeze instances.
Note
  • DataWorks regularly generates instances for auto triggered nodes. The generated instances run 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.

Manage auto triggered node instances in the 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.

Operation Description
Filter Find required instances by setting parameters in the red box marked with 1 in the preceding figure.

You can search for instances by node name or node ID and set 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 to filter instances.

Note By default, the data timestamp is set to the previous day of the current day.
Stop Stop the instance. You can only stop instances in the Pending (Resource) or Running state. After you perform this operation, the instance enters the Failed state.
Rerun Rerun the instance. After the instance is rerun, its descendant instances will be run as scheduled. Perform this operation if an instance fails or it is not run as scheduled.
Note This operation only applies to instances in the Pending (Ancestor), Successful, or Failed state.
Rerun Descendant Nodes Rerun the instance and its descendant instances. You must specify the instances to rerun. After they are run, their descendant instances will be run as scheduled. This operation applies to data recovery.
Note You can only select instances in the Pending (Ancestor), Successful, or Failed state. If you select an instance in another state, Meet Rerun Condition appears as No and you cannot run the instance.
Set Status to Successful Set the status of the instance to Successful and run its descendant instances as scheduled. You can perform this operation if an instance fails.
Note This operation only applies to failed instances but not 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, DataWorks automatically runs this instance after running its ancestor instances.
  • If all the ancestor instances are run, the instance is directly set to Failed. You must manually rerun the instance.
Batch operations Select multiple instances and click a button in the red box marked with 3 in the preceding figure to perform batch operations. The buttons include Stop, Rerun, Set Status to Successful, Freeze, and Unfreeze.

Manage auto triggered node instances in a 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.

Operation Description
Show Ancestor Nodes and Show Descendant Nodes Show ancestor or descendant instances at one or more levels. If a workflow contains three or more instances, the DAG only displays the current instance and hides its ancestor and descendant instances.
View Runtime Log View the operational logs of the instance if it is in the Running, Successful, or Failed state.
View Code View the code of the instance.
Edit Node Go to the DataStudio page to modify the node to which the instance belongs.
View Affected Nodes Go to the Instance Information page to view the basic information, affected baselines, and running information of the instance.
View Lineage View the lineage of the instance.
More View more instance information on the General, Context, Runtime Log, Operation Log, and Code tabs.
Stop Stop the instance if it is in the Pending (Resource) or Running state. After you perform this operation, the instance enters the Failed state.
Rerun Rerun the instance. After the instance is rerun, its descendant instances will be run as scheduled. Perform this operation if an instance fails or it is not run as scheduled.
Note This operation only applies to instances in the Pending (Ancestor), Successful, or Failed state.
Rerun Descendant Nodes Rerun the instance and its descendant instances. You must specify the instances to rerun. After they are run, their descendant instances will be run as scheduled. This operation applies to data recovery.
Note You can only select instances in the Pending (Ancestor), Successful, or Failed state. If you select an instance in another state, Meet Rerun Condition appears as No and you cannot run the instance.
Set Status to Successful Set the status of the instance to Successful and run its descendant instances as scheduled. You can perform this operation if an instance fails.
Note This operation only applies to failed instances but not workflows.
Resume Continue to run the instance after it fails.
Emergency Operations Perform these operations in emergency only. These operations only take effect for the current instance for one time.

Select Delete Dependencies to delete dependencies of the current instance. You can perform this operation so that you can start the current instance 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, DataWorks automatically runs this instance after running its ancestor instances.
  • If all the ancestor instances are run, the instance is directly set to Failed. You must manually rerun the instance.

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.

Instance statuses

No. Status Icon
1 Successful 1
2 Pending (Ancestor) 2
3 Failed 3
4 Running 4
5 Pending (Resource) 5
6 Pending (Schedule) 6