This topic describes how to troubleshoot issues if an auto triggered node that has instances but the instances are not run.

What do I do if the specified auto triggered node has instances but the instances are not run?

Troubleshooting: Right-click a dimmed instance of the specified auto triggered node in the directed acyclic graph (DAG) and select Show Ancestor Nodes to check whether the ancestor nodes are in the state of running, run failed, pending, or unfrozen. The auto triggered node is not run if its ancestor nodes fail to be run.

Status of the ancestor nodes
  1. Frozen (purple): An instance that is frozen is marked in purple. In this case, the auto triggered node and its descendant nodes are not run. Click the auto triggered node. In the window that appears in the lower-right corner of the page, click Show Details, and view the operation log of the node on the Operation Log tab.
  2. Pending (yellow): A node that is waiting for its scheduled time to arrive is marked in yellow. Click the node. In the window that appears in the lower-right corner of the page, click Show Details, and view the scheduled time of the node on the General tab. An auto triggered node that is waiting for scheduling resources is marked in yellow. If a note about waiting for scheduling resources appears in a log, the number of auto triggered nodes that are running in the current workspace has reached the upper limit. Right-click the auto triggered node and select Instance Diagnose. On the Intelligent Diagnosis page, check which nodes are running while the current auto triggered node is waiting for scheduling resources.
  3. To be run (dimmed): Right-click a dimmed instance of the auto triggered node and select Show Ancestor Nodes to check the status of each ancestor node. We recommend that you use the intelligent diagnosis and ancestor node analysis features. Ancestor node analysis
Possible causes
  1. An auto triggered node is run as scheduled if the node is not frozen and the following information is provided: scheduling resources, scheduled time, and the status of each ancestor node.
  2. If the ancestor nodes are not in the preceding states and the entire workflow is dimmed, the ancestor node dependency is changed and the entire workflow is isolated.
Instance status

Why is the auto triggered node not run when the scheduled time arrives?

In some cases, the time at which an auto triggered instance is scheduled to run may not be the same as the time at which the instance is actually run.

In this case, we recommend that you use the ancestor node analysis and intelligent diagnosis features to identify and fix issues at the earliest opportunity.

Ancestor node analysis and intelligent diagnosis
The following conditions must be met if you want to run a node in DataWorks:
Notice The following figure shows a three-level node dependency. In actual scenarios, you may need to configure more than three levels of nodes in a dependency. However, the logic of the dependency is the same. You can right-click a dimmed node and select Show Ancestor Nodes to view the status of each ancestor node of the node.
  1. All the ancestor nodes of the current auto triggered node have finished running. A node that is successfully run is marked in green. You can view the status of each ancestor node of the auto triggered node in a DAG in Operation Center.Status

    Example: The current time is 01:00. Node A2 is scheduled to run at 01:00, Node A3 is scheduled to run at 03:00, and Node B is scheduled to run at 00:00. Node B depends on Nodes A2 and A3.

    Analysis: The time at which Node B is scheduled to run has arrived. However, the time at which the ancestor nodes of Node B are scheduled to run has not arrived. In this case, Node B cannot be run until the scheduled time of the ancestor nodes A2 and A3 arrives and the ancestor nodes A2 and A3 are successfully run. If Node A2 or Node A3 fails to be run as scheduled, Node B cannot be run as scheduled.

  2. The scheduled time of the node has arrived. A node that is waiting for its scheduled time to arrive is marked in yellow.Status

    Example: The current time is 04:00. Node A2 is scheduled to run at 01:00, Node A3 is scheduled to run at 03:00, and Node B is scheduled to run at 05:00. Node B depends on Nodes A2 and A3.

    Analysis: Node B is scheduled to run at 05:00 and Nodes A2 and A3 are successfully run. However, the time at which Node B is scheduled to run has not arrived and therefore the instance status of Node B is waiting for its scheduled time to arrive.

  3. The scheduling resources in a workspace are sufficient to run nodes. An auto triggered node that is waiting for scheduling resources is marked in yellow. This is because the number of auto triggered nodes that are running by using the scheduling resources in a workspace has reached the upper limit and the current node is waiting for gateway resources.Status

    Example: The current time is 04:00. Node A2 is scheduled to run at 01:00, Node A3 is scheduled to run at 03:00, and Node B is scheduled to run at 00:00. Node B depends on Nodes A2 and A3.

    Analysis: Node B is scheduled to run at 00:00 and Nodes A2 and A3 are successfully run. However, the scheduling resources that are used to run Node B are insufficient. As a result, the instance status of Node B is waiting for scheduling resources.

    If Node B is run by using an exclusive resource group for scheduling and you want to view the resource usage of this group, you can use one of the following methods: 1. Log on to the DataWorks console. On the Resource Groups page, view the nodes that run on the exclusive resource group for scheduling and the usage of this resource group. For more information, see View the resource usage of an exclusive resource group. 2. Right-click an instance and select Instance Diagnose to check the nodes that are occupying resources in the exclusive resource group for scheduling.

  4. The node is normally run as scheduled and is not frozen. A node that is frozen is marked in purple.Status

    Example: The current time is 04:00. Node A2 is scheduled to run at 01:00 and its status is scheduling suspended, Node A3 is scheduled to run at 03:00, and Node B is scheduled to run at 00:00. Node B depends on Nodes A2 and A3.

    Analysis: The preceding information indicates that a node can be run as scheduled only after all of its ancestor nodes are successfully run. The preceding figure on the left shows that Node A2 is frozen. As a result, Node B cannot be run. The preceding figure on the right shows that all the ancestor nodes of Node B are successfully run but Node B cannot be run as scheduled. This is because Node B is frozen. For more information, see Node freezing and unfreezing.

  5. If none of the preceding conditions are met, check whether the auto triggered node is an isolated node. For more information, see Isolated nodes.