Conditions

Condition is a conditional node, that determines which downstream task should run based on the condition of the upstream task. Currently, the Conditions support multiple upstream tasks, but only two downstream tasks. When the number of upstream tasks exceeds one, achieve complex upstream dependencies by through and and or operators.

Create Task

Click Project Management -> Project Name -> Workflow Definition, and click the Create Workflow button to enter the DAG editing page.
Drag from the toolbar task node to canvas.

Task Parameters

Parameter	Description
Node Name	Set the name of the task. Node names within a workflow definition are unique.
Run flag	Indicates whether the node can be scheduled normally. If it is not necessary to execute, you can turn on the prohibiting execution switch.
Description	Describes the function of this node.
Task priority	When the number of worker threads is insufficient, they are executed in order from high to low according to the priority, and they are executed according to the first-in, first-out principle when the priority is the same.
Worker group	The task is assigned to the machines in the worker group for execution. If Default is selected, a worker machine will be randomly selected for execution.
Task group name	The group in Resources, if not configured, it will not be used.
Environment Name	Configure the environment in which to run the script.
Number of failed retries	The number of times the task is resubmitted after failure. It supports drop-down and manual filling.
Failure Retry Interval	The time interval for resubmitting the task if the task fails. It supports drop-down and manual filling.
Timeout alarm	Check Timeout Alarm and Timeout Failure. When the task exceeds the "timeout duration", an alarm email will be sent and the task execution will fail.
Downstream tasks selection	Depending on the status of the predecessor task, you can jump to the corresponding branch, currently two branches are supported: success, failure Success: When the upstream task runs successfully, run the success branch. Failure: When the upstream task runs failed, run the failure branch.
Upstream condition selection	Can select one or more upstream tasks for conditions. Add an upstream dependency: the first parameter is to choose a specified task name, and the second parameter is to choose the upstream task status to trigger conditions. Select upstream task relationship: use `and` and `or` operators to handle the complex relationship of upstream when there are multiple upstream tasks for conditions.

Related Task

switch: Conditions task mainly executes the corresponding branch based on the execution status (success, failure) of the upstream nodes. The Switch task node mainly executes the corresponding branch based on the value of the global parameter and the result of user written expression.

Example

This sample demonstrates the operation of the Condition task by using the Shell task.

Create workflow

Go to the workflow definition page, and then create the following task nodes:

Node_A: Shell task, prints out "hello world", its main function is the upstream branch of Condition, and triggers the corresponding branch node according to whether its execution is successful or not.
Condition: The Conditions task executes the corresponding branch according to the execution status of the upstream task.
Node_Success: Shell task, print out "success", Node_A executes the successful branch.
Node_False: Shell task, print out "false", Node_A executes the failed branch.

condition_task01

View the execution result

After you finish creating the workflow, you can run the workflow online. You can view the execution status of each task on the workflow instance page. As shown below:

condition_task02

In the above figure, the task status marked with a green check mark is the successfully executed task node.

Note

The Conditions task supports multiple upstream tasks, but only two downstream tasks.
The Conditions task and the workflow that contain it do not support copy operations.
The predecessor task of Conditions cannot connect to its branch nodes, which will cause logical confusion and does not conform to DAG scheduling. The situation shown below is wrong.

condition_task03 condition_task04