This topic provides answers to some frequently asked questions about node instances.

What do I do if I cannot find the desired auto triggered node on the Cycle Task page in Operation Center?

The auto triggered node is not deployed to the production environment. Check whether the deployment fails.

Why cannot I find even one instance of an auto triggered node?

[Troubleshooting] Check whether the Periodic Scheduling switch is turned on in the Scheduling Properties section on the Configuration page. If you want to turn on the switch, use the Alibaba Cloud account to go to the Configuration page and turn on the Periodic Scheduling switch in the Scheduling Properties section. Turn on the Periodic Scheduling switch

What do I do if I can find instances of other auto triggered nodes but cannot find even one instance of the desired auto triggered node?

[Troubleshooting] Scenario 1: Check whether the desired auto triggered node is deployed after 23:30.

[Troubleshooting] Scenario 2: Right-click the desired auto triggered node in the canvas and select Show Ancestor Nodes to check whether the auto triggered node has ancestor nodes. If the auto triggered node has no ancestor nodes and becomes an isolated node, after you receive a node isolation alert, you must handle the alert at the earliest opportunity.

[Solution] The node dependency is changed. The auto triggered node does not have ancestor nodes. Submit the dependency of the auto triggered node again.

[Troubleshooting] Scenario 3: Check whether the auto triggered node and its ancestor nodes are within the validity period. A deprecated auto triggered node does not generate instances. On the Properties tab of the DataStudio page, change the value of the Validity Period parameter in the Schedule section. Scheduling Effective Period

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

[Troubleshooting] Right-click a dimmed instance of the desired auto triggered node 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.

Note For more information, see Nodes that are not run.
[Ancestor node status]
  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 run 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.

    If all the instances are dimmed, check whether the auto triggered node is an isolated node by referring to the question "What do I do if I can find instances of other auto triggered nodes but cannot find even one instance of the desired auto triggered node?" in this topic.

Note We recommend that you use the intelligent diagnosis and ancestor node analysis features.
Instance Diagnose
[Cause]
  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.

What are the conditions that must be met to run a node?

  1. The scheduled time of the node has arrived. The node that is waiting for its scheduled time to arrive is marked in yellow.
  2. The running of all the ancestor nodes of the current auto triggered node is complete. An ancestor 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 directed acyclic graph (DAG) in Operation Center.
  3. The resources in a workspace are sufficient to run nodes. An auto triggered node that is waiting for scheduling resources is marked in yellow. The operation log shows that the number of auto triggered nodes that are run in parallel in the workspace has reached the upper limit and the current node is waiting for gateway resources.
  4. The node is run as scheduled. A node that is frozen is marked in purple.