Test instances are generated when you test auto triggered nodes. You can manage test instances.

Manage test instances in the instance list

You can manage test instances in the instance list. For example, you can rerun, freeze, or unfreeze instances, set the status of instances to Successful, view the lineage of instances, and check operational logs.

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 Owner, Run At, Data Timestamp, Status, Region, Engine type, Engine instance, Baseline, My Nodes, Tested by Me Today, and Frozen to filter instances.

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.
More Click More in the Actions column and then select an operation. The operations include Set Status to Successful, Freeze, Unfreeze, View Lineage, and View Runtime Log.
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 test 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
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 Lineage View the lineage of the instance.
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.
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 Pause the scheduling of the instance.
Unfreeze Resume the scheduling of 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.

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