Node Disabling

Version

Application Scenario

You may want to disable nodes or operators in the following scenarios:

• Some nodes or operators are temporarily not needed but may need to be executed later, so you do not want to delete them.

• Some nodes or operators are added for debugging but you do not want to delete them after debugging.

• In complex scheduled tasks, if you need to remove certain nodes or operators for debugging, you have to copy the entire task as a backup and then delete the nodes or operators, which is cumbersome.

Function Overview

1. You can disable a node and its downstream nodes, as shown in the following figure.

2. You can disable an operator and its downstream operators, as shown in the following figure.

Disabling a Node

Right-click the node you want to disable and select Disable Node and Its Downstream Nodes to disable the node and its downstream nodes, as shown in the following figure.

Logic description:

1. An inheritance relationship exists between a disabled node and its subsequent nodes. This means that if you disable a subsequent node first and then disable the preceding node, the disabled status of the subsequent node will be overriden by the inherited status from the preceding node. If the preceding node is re-enabled, the subsequent node will also be re-enabled.

2. Disabled nodes can be connected to other nodes. If a node is connected after a disabled node, it will inherit the disabled status from the preceding node. If it is connected to a normal node, it will not be affected.

3. After a Loop Container node is disabled, all nodes within the Loop Container node will be disabled. You cannot individually re-enable or disable any node within the Loop Container node but can re-enable the Loop Container node to allow all nodes within it to run again.

4. Disabled nodes also support editing and modification, in the same way as normal nodes.

Cancelling Disabling

After disabling a node, you can re-enable it by selecting Cancel Disabling Node and Its Downstream Nodes, as shown in the following figure.

Logic description: This function only supports node disabling or re-enabling from the source node, and you are not allowed to change the status of intermediate nodes. If you delete the connector, the subsequent nodes will return to normal status.

Description of N to 1/1 to N Scenario

Scenario	Description
	1. If any of nodes A, B, or C is disabled, nodes D, E, and F are all disabled and will not execute. 2. When nodes A, B, and C are all restored to normal status, nodes D, E, and F will also return to normal status. 3. If node D is disabled first and then node A is disabled, node D will inherit the disabled status of node A, and its original disabled status will be overriden.If node A is re-enabled, nodes D, E, and F will all be re-enabled. 4. If node D is disabled and node A is normal, node A can connect to node D without affecting the workflow. If node A is disabled and connected to node D, node D will inherit the disabled status from node A. 5. If node D is disabled and the connectors connecting node D with node E and node F are deleted, nodes E and F will return to normal status, while node D remains disabled.
	If node A is disabled, nodes B, C, D, and E will all be disabled, and nodes A, B, C, D, and E will not execute.

Disabling an Operator

In the Data Transformation node, you can disable an operator and its downstream operators, as shown in the following figure.

Logic description:

1. An inheritance relationship exists between a disabled operator and its subsequent operators. This means that if you disable a subsequent operator first and then disable the preceding operator, the disabled status of the subsequent operator will be overriden by the inherited status from the preceding operator. If the preceding operator is re-enabled, the subsequent operator will also be re-enabled.

2. Disabled operators can be connected to other operators. If an operator is connected after a disabled operator, it will inherit the disabled status from the preceding operator. If it is connected to a normal node, it will not be affected.

3. Disabled operators also support editing and modification, in the same way as normal operators.

4. Disabled operators still require you to validate connector restrictions.

As shown in the following figure, the DB Table Input operator cannot be connected to the Field Setting operator. You need to remove the connector between the DB Table Input operator and the Data Filtering operator first.

5. Data distribution logic after output operators are disabled:

• You can distribute data to disabled output operators, but the configuration will not take effect during execution.

• If some output operators are disabled while others remain enabled, the data distribution can be performed normally.

If all output operators are disabled, the system will report an error in the Data Transformation node.

Cancelling Disabling

After disabling an operator, you can re-enable it by clicking Cancel Disabling Node and Its Downstream Nodes, as shown in the following figure.

Logic description: This function only supports node disabling or re-enabling from the source node, and you are not allowed to change the status of intermediate nodes. If you delete the connector, the subsequent nodes will return to normal status.

For nodes such as Parameter Assignment, Conditional Branch, and Virtual Node that do not support independent execution, if their downstream nodes are set to Disable Node and Its Downstream Nodes, you cannot perform Run Node and Its Downstream Nodes on these nodes, as shown in the following figure.