This topic provides answers to some frequently asked questions about isolated nodes.

What is an isolated node?

An isolated node is a node that does not depend on any ancestor node. You can view its ancestor nodes on the Cycle Task or Cycle Instance page after you right-click the node and select Show Ancestor Nodes. This type of node cannot be run as scheduled. If an isolated node has too many descendant nodes, serious risks may arise. A node isolation alert is automatically reported if an isolated node is identified. We recommend that you handle the alert at the earliest opportunity. Isolated nodes

How can I fix an isolated node?

  1. Possible causes and solutions:
    • An isolated auto triggered node has no ancestor nodes and you cannot find its ancestor nodes on the Cycle Task or Cycle Instance page in the production environment in Operation Center. In this case, configure ancestor nodes for the isolated auto triggered node again, deploy the ancestor nodes, and then check whether the node is successfully deployed on the Cycle Task page in Operation Center.
    • Ancestor nodes are out of the validity period for scheduling. To resolve this issue, specify Validity Period in the Schedule section on the Properties tab of the DataStudio page.
    • The desired auto triggered node and its ancestor node reside in different workspaces and the Periodic Scheduling switch is turned off for the workspace in which the ancestor node resides. Contact the owner of the workspace to turn on the Periodic Scheduling switch or delete the cross-workspace node dependency. Cross-workspace node dependency
    • The output name of the ancestor node is changed or deleted.
    Warning If you forcibly change the value of the Parent Node Output Name parameter, all descendant nodes may not be run as scheduled. Exercise caution when you perform this operation. Before you undeploy a node, delete the dependencies between this node and all its descendant nodes.
  2. Workaround for the case that an isolated node has descendant nodes:
    Descendant nodes of an isolated node cannot run. In an emergency situation, you can delete the dependency of your node on an isolated node if you confirm that your node can generate data as expected even if its dependency on the isolated node is deleted. Delete dependency
  3. Change the node isolation alert recipient:
    Isolated Node Alert Rule is a default rule. By default, a node isolation alert is sent to the owner of the node. You can use the Alibaba Cloud account to enable or disable the rule. You can click View Details in the Actions column that corresponds to the node isolation alert rule to change the alert notification method and add other alert recipients. Node isolation alert recipient