Problem description
Possible cause
The ancestor node of the node fails to be run. The possible cause is that the instance generated by the ancestor node is frozen or waiting to be run. The node can be run only after the running of the ancestor node is successful.
Solution
- Purple
The color purple indicates that the instance generated by the ancestor node is frozen, and both the ancestor node and the node fail to be run. In this case, you can view the operation record of the frozen instance on the instance information page of the instance.
- Yellow
The color yellow indicates that the ancestor node is waiting to be run.
- The ancestor node is scheduled to be run, but the scheduled time does not arrive. In this case, you can select the ancestor node and click Show Details in the lower-right corner to view the scheduled time for running the ancestor node. When the scheduled time arrives, the system starts to run the ancestor node. After the running of the ancestor node is complete, the system starts to run the node.
- The ancestor node may be waiting for scheduling resources. You can view the operational logs of the ancestor node to check whether the ancestor node is waiting for scheduling resources. If the ancestor node is waiting for scheduling resources, the scheduling resources used by the running nodes in the current workspace have reached the upper limit. You can adjust the scheduled time for running the ancestor node or purchase an exclusive resource group for scheduling to run the ancestor node. For more information about exclusive resource groups for scheduling, see Exclusive resource groups for scheduling.
- Gray
The color gray indicates that the ancestor node fails to be run. In this case, you must view the status of the ancestor node of the current ancestor node.