A CONDITIONS node is a conditional node that determines which descendant node is run based on the status of ancestor nodes. A CONDITIONS node can have multiple ancestor nodes and only two descendant nodes. If the number of ancestor nodes is greater than one, you can use the AND or OR operator to implement complex dependencies between the CONDITIONS node and its ancestor nodes. This topic describes the parameters that are involved when you create a CONDITIONS node.
Parameter | Description |
Node Name | The name of the node. A node name is unique in a workflow. |
Run flag |
|
Description | The feature description of the node. |
Task priority | The priority of the node in the workflow. Default value: MEDIUM. Valid values:
|
Number of failed retries | The maximum number of times that the system automatically retries to run the node if the workflow fails. |
Failed retry interval | The interval between two consecutive retries. Unit: minutes. |
State | The state of the ancestor node. Valid values: Success and Failed. |
Branch flow | After you connect descendant nodes to the CONDITIONS node, you can configure descendant branches. If all the ancestor nodes meet the specified check conditions, the Success branch is run. If at least one ancestor node does not meet the specified check conditions, the Failed branch is run. |
Timeout alarm | Specifies whether to enable alerting on node execution timeout. By default, the Timeout alarm switch is turned off. You can turn on the Timeout alarm switch and select Timeout alarm and Timeout failure as Timeout strategy. If the execution of a node exceeds the timeout period, an alert message is sent to your mailbox, and the node fails. |
Add pre task check condition | The check conditions for ancestor nodes. A descendant branch is run based on the status of ancestor nodes.
|
Pre tasks | The ancestor node of the current node. One or more ancestor nodes are supported. |