Use this topic to diagnose why auto triggered node instances are missing or not running in DataWorks Operation Center.
In normal operation, a node is deployed to the production environment, an instance is generated the next scheduling cycle, the instance waits for its scheduled time, and then runs after all ancestor nodes finish successfully.
Instance states at a glance
| State | Color | Meaning | Terminal? |
|---|---|---|---|
| To be run | Gray (dimmed) | Waiting for ancestor nodes to finish or for dependencies to resolve | No |
| Waiting | Yellow | Waiting for scheduling time or for scheduling resources | No |
| Running | — | Currently executing | No |
| Successfully run | Green | Completed without errors | Yes |
| Run failed | — | Execution failed | Yes |
| Frozen | Purple | Manually frozen; node does not run and blocks descendant nodes | Yes (until unfrozen) |
Why doesn't my node appear on the Cycle Task page?
The node hasn't been deployed to the production environment. Check whether the deployment failed.
Why does my auto triggered node have zero instances?
Scheduling is not enabled for the workspace. In DataStudio, go to Settings > Scheduling Settings and check whether Periodic scheduling is turned on for the workspace.
To turn on Periodic scheduling, sign in with an Alibaba Cloud account.
Why do other nodes have instances but this specific node doesn't?
Check the following causes in order:
-
Deployed after 23:30? Nodes deployed after 23:30 don't generate instances until the next day.
-
Isolated node? Right-click the directed acyclic graph (DAG) of the node and check whether the node has no dependencies and has become isolated. If you see an isolation notification, re-commit the node dependencies.
-
Expired validity period? Expired nodes don't generate instances. On the Properties tab in DataStudio, update the Validity Period parameter for the node.
-
Instance Generation Mode set to Next Day? If the node was newly created and Instance Generation Mode is set to Next Day, no instance is generated on the day of creation.
Why do instances exist but not run?
An ancestor node is blocking execution. Right-click the DAG of a gray (dimmed) instance and select Show Ancestor Nodes to view ancestor instances across multiple levels. Check whether ancestor instances are in the Not running, Running, Run failed, Waiting, or Frozen state:
Frozen (purple) — The ancestor is manually frozen, which blocks all descendant nodes. Click Show Details in the lower-right corner of the page, then open the Operation Log tab to review operation history.
Waiting (yellow) — Two possible causes:
-
*Waiting for scheduling time*: Click Show Details and open the General tab to see when the instance is scheduled to run.
-
*Waiting for scheduling resources*: The number of auto triggered nodes running in parallel has reached the upper limit. Right-click the instance, select Instance Diagnose, and check the Resources step on the End-to-end Diagnostics tab to identify which nodes are holding resources.
To be run (dimmed) — Right-click the instance and select Show Ancestor Nodes to trace the dependency chain further upstream.
If every instance in the workflow is dimmed, the workflow may be isolated. See Why do other nodes have instances but this specific node doesn't? for how to diagnose isolated nodes.
Use the intelligent diagnosis and upstream analysis features to speed up root cause identification.
What conditions must be met for a node to run?
A node runs only when all four conditions are satisfied:
-
Scheduling time has arrived — Instances waiting for their scheduled time show as yellow.
-
All ancestor nodes have finished running — Successfully run nodes show as green. Check ancestor status in the DAG in Operation Center.
-
Scheduling resources are available — If the logs show that the parallel limit has been reached and the node is waiting for gateway resources, the instance shows as yellow.
-
Node is not frozen — Frozen nodes show as purple.