Run Modes

LAST UPDATED: JUNE 23, 2025

Run Mode Summary

Run Mode	Trigger Condition	Execution Count
Wait for Any, Run Always	Executes when any one immediate upstream task completes	Executes once per completed upstream path
Wait for Any, Run Once	Executes when any one immediate upstream task completes	Executes once
Wait for All	Waits for all immediate upstream tasks to complete	Executes once

Wait for Any, Run Always DEFAULT

Functionality

The Wait for Any, Run Always (default) run mode allows a task to execute each time any one of its direct predecessor tasks completes.

It is particularly beneficial when a playbook task must respond to upstream parallel paths independently and sequentially, triggering a separate execution instance each time one of them completes.

Example - Wait for Any, Run Always

SCENARIO – Task D is configured with the Wait for Any, Run Always run mode.

Before Execution

Task D receives parallel input from three tasks—A, B, and C. Task A has a 30-second delay, task B has a 60-second delay, and task C proceeds without delay before all three converge at task D.

During Execution

Task C completes and triggers task D to execute. Although tasks A and B also finish, their delay tasks block further execution from reaching task D. Therefore, task D runs only once.

Continued Execution

Task D executes a second time after task A's delay completes. This reflects an additional instance of task D's execution. Task B remains paused in its 60-second delay.

Final State

All upstream tasks have completed, and task D has executed once for each path. This results in a total of three executions.

Resulting Instances

The Playbook Task Details panel shows all execution instances of the task. Completed instances appear in the instance selector for easy review.

Wait for Any, Run Once

Functionality

The Wait for Any, Run Once run mode permits a task to execute a single time as soon as any one of its direct predecessor tasks completes.

This is useful in workflows where an early upstream result is sufficient to proceed, such as initiating a failover, sending an alert, or short-circuiting a process based on the first available condition.

Example - Wait for Any, Run Once

SCENARIO – Task D is configured with the Wait for Any, Run Once run mode.

Before Execution

Task D, whose run mode is set to Wait for Any, Run Once, converges from three tasks—A, B, and C. Task A leads with a 30-second delay, while task B follows with a 60-second delay. Task C has no delay. All tasks independently converge at task D.

During Execution

Tasks A, B, and C have started. Task A's delay is actively progressing toward completion. Task D has not yet executed. Task B is paused in its 60-second delay.

Continued Execution

Task A's delay has completed but does not trigger task D to execute.

KEY POINT

Task D does not run again, even if additional execution paths reach it after the first.

Final State

All upstream tasks have completed, but task D ran only once.

Wait for All

Functionality

The Wait for All run mode permits a task to execute a single time as soon as all direct predecessor tasks complete.

This is beneficial in scenarios that require complete readiness of prerequisite data and the prevention of redundant downstream task execution.

NOTICE

In business workflows where a downstream task receives input from multiple execution instances of an upstream task, use a Merge task to consolidate those inputs.

Example - Wait for All

SCENARIO – Task D is configured with the Wait for All run mode.

Before Execution

Task D, whose run mode is set to Wait for All, receives convergence from three parallel tasks—A, B, and C—with task C preceding a 3-second delay before joining.

During Execution

Tasks A, B, and C have completed. The 3-second delay following task C is delaying its progression to task D. Task D remains in a waiting state.

OBSERVATION

Note that the execution status icon for task D is Group 125.png instead of .

This signifies that task D has not yet executed, as the Wait for All run mode mandates completion of all upstream tasks prior to its initiation.

After Execution

All parallel tasks have completed, allowing task D to execute and finish.