Run a test on an Auto-triggered Task to verify that it executes correctly in the Production Environment. Each test generates a Test Instance that you can monitor and manage in Operation Center.
A test run executes the actual code logic. Proceed with caution.
Run a test and generate a test instance
-
Go to Operation Center. Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left navigation pane, choose Data Development and O&M > Operation Center. Select the desired workspace from the drop-down list and click Go to Operation Center.
-
Go to Auto Triggered Task O&M > Auto Triggered Nodes.
-
Run a test using one of the following methods:
-
List view: Find the task and click Test in the Actions column. If the page is not in list view, click the
icon in the middle of the page to switch views. -
DAG view: Right-click the target node and select Test from the menu. If the page is not in DAG view, find the task and click DAG in the Actions column to open its DAG.
-
-
Configure the parameters in the Test dialog box.
Parameter Description Test Name Enter a name for the test. Data Timestamp Select the data timestamp. If you select a date before yesterday, the task runs immediately. If you select yesterday, the task runs at its scheduled time. Advanced configuration Enable to assign values to scheduling parameters. These assignments apply only to the current test. 
View the test instance list
The Test Instance list shows instances generated from tests, along with their execution status and available actions.
Filter instances (Area 1)
Filter by task name, task ID, Node Type, Run At, Data Timestamp, Scheduling Resource Group, My Node, The node I tested today, or Pause (freeze) a node. The data timestamp defaults to the day before the current date.
Instance list (Area 2)
Lists the Test Instances that match your filter criteria. Up to 200 instances are displayed per page (configurable in Area 5).
Instance actions (Area 3)
Right-click or use the Actions column to perform the following operations:
| Action | When to use | State requirement | Result |
|---|---|---|---|
| DAG | View upstream and downstream dependencies for the instance. | Any | Opens the instance DAG. For details, see Appendix: DAG features. |
| To diagnose (Intelligent Diagnosis) | Locate why a task did not run as expected. | Any | Runs an end-to-end analysis. For details, see Intelligent Diagnosis. |
| Rerun | Re-execute a task after it finishes. | Succeeded or Failed | Reruns the task. A successful rerun triggers scheduling of downstream tasks that have not yet run. |
| Rerun Descendent Nodes | Re-execute downstream nodes selectively after a task finishes. | Succeeded or Failed | Opens a dialog to select and rerun downstream nodes. A successful rerun triggers scheduling of downstream tasks that have not yet run. Selecting nodes in other states prevents submission. |
| Set to Succeeded | Unblock downstream tasks when a failed task does not need to be rerun. | Failed | Changes the instance status to Succeeded, allowing downstream tasks to proceed. |
| Stop | Cancel a task that no longer needs to run. | Pending (Schedule), Pending (Resources), or Running | Stops the task. The instance status changes to Failed. |
| Freeze | Suspend a task and its downstream tasks for a period of time. | Any | Freezes the instance. For details, see Manage Auto-triggered Tasks. Do not freeze the projectname_root node — it is the root node of the workspace and all Auto-triggered Task instances depend on it. If you freeze this node, instances of Auto-triggered Tasks cannot run. |
| Unfreeze | Resume a frozen instance. | Frozen | If the instance has not yet run, it runs automatically after upstream tasks complete. If all upstream tasks are already complete, the instance status is set to Failed and you must manually rerun it. Note: this affects only the current instance — if the Auto-triggered Task itself is still frozen, the next day's instance will also be Frozen. |
| View Lineage | Inspect data lineage for the instance. | Any | Opens the lineage view. |
| View Node Details | View basic information about the instance. | Any | Opens the node details panel. |
| View Runtime Log | Review the detailed execution process. | Running or completed | Opens the runtime log. For log parameter descriptions, see Appendix: Runtime log parameters. |
Batch operations (Area 4)
Select multiple instances to perform: Stop, Rerun, Set to Succeeded, Change Resource Group, Freeze, Unfreeze, or Export Query Results.
Test instance DAG
In list view, click a Test Instance name or click DAG in the Actions column to open its DAG. Right-click any node in the DAG to perform actions.
DAG panel features (Areas 1–2)
-
Search (Area 1): Find instances by Node Name, Node ID, Instance ID, or instance name.
-
Display controls (Area 2): Use the icons in the upper-right corner to adjust the view. From left to right: Open Map/Close Map, Show Alert Status/Hide Alert Status, Update Node Status, Zoom In, Zoom Out, Set the canvas to a 1:1 ratio, Automatically Fit Screen, Toggle Full Screen View.
Single instance operations
Right-click a node to access:
-
View Code: View the node's code in the Production Environment. If the code is not as expected, verify that the latest version has been published.
-
Edit Node: Opens the node in DataStudio.
For all other actions, see View the test instance list.
Instance details panel (Area 4)
Click a node to open the details pane:
-
View Logs: View the detailed execution process of a running or completed task. For log parameter descriptions, see Appendix: Runtime log parameters.
-
Show Details: View full instance details. See Instance details.
Instance details
In DAG view, click an instance and then click Show Details in the lower-right pane. This opens the instance details page.
| Tab | Content |
|---|---|
| General | Scheduling properties of the task in the Production Environment. Includes instance status, time waiting for resources, run duration, rule monitoring (you can only view details of rules that monitor task run status, not data quality monitoring rules), baseline monitoring, and maximum parallel instances (Unlimited or 1–10,000). For parameter descriptions, see Configure resource properties. |
| Runtime Log | Detailed execution process of a running or completed task. For log parameter descriptions, see Appendix: Runtime log parameters. |
| Operation Log | Operation records for the task or instance, including time, operator, and action. |
| Code | Latest code for the task in the Production Environment. If the code is not as expected, verify that the latest version has been published. See Publish tasks. |
Troubleshooting instance status on the General tab:
-
Not Run / Pending (Schedule) / Pending (Resources) / Frozen: See Task run conditions for troubleshooting steps.
-
Long resource wait time: Use Intelligent Diagnosis to identify which tasks are occupying resources.
-
Excessive run duration: For non-synchronization tasks, consult the engine owner. For offline synchronization tasks, see Offline synchronization common issues.
Limits
Instance and log retention
| Resource group type | Instance retention | Log retention |
|---|---|---|
| Public Scheduling Resource Group | 30 days | 7 days |
| Exclusive Scheduling Resource Group | 30 days | 30 days |
Additional constraints:
-
You cannot manually delete a Test Instance. Test Instances are deleted automatically after approximately 30 days. To stop a task from running without deleting its instances, freeze the instances instead.
-
If logs for a completed instance exceed 3 MB, the system periodically clears them.
Concurrency
When Maximum Parallel Instances is configured for a task, Test Instances share the concurrency quota with auto-triggered instances and backfill instances. When multiple instance types queue simultaneously, backfill instances for non-current days have their priority lowered from 8 to 3.
Edition and permission requirements
DataWorks Professional Edition and higher unlock the following features in Operation Center:
-
Intelligent Diagnosis: Quickly locate task run issues. A free trial is available.
-
Advanced DAG analysis: Node aggregation, upstream analysis, and downstream analysis for complex task lineage.
-
Export query results: Export instance data for external reports or further analysis.
Some features are available only to users with O&M permissions. If a feature is grayed out or unavailable, go to the management and control overview page, click Workspace Members and Roles in the left navigation pane, and check your permissions on the Workspace Members tab.