Run parallel paths

Use the Run parallel paths action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to run multiple branches (paths) of actions simultaneously.

Note: This video was recorded using the previous user interface, so you may notice differences in the layout and menus. While the overall functionality remains the same, the user interface and navigation steps may vary slightly.

Before you begin: 

  • Understand Variables

  • Understand container actions. You can add actions to create branches such as Branch by stage or to contain other actions such as Action Set that can be collapsed down into a single action high-level view.

Jump to:

Configure the Run parallel paths action

See the Run parallel paths fields, buttons, and settings table for all the configuration fields.

  1. Open the designer canvas, add the action to the designer canvas, and open the action configuration panel. For more information, see Designer canvas.

  2. Type in the Branches fields to rename the default branches.
  3. To add another branch, click Add new branch.
    4. Important: 

    • The maximum number of branches you can add is 20.

    • If a Run parallel paths action has child Run parallel paths actions, the combined branches of the parent and child Run parallel paths actions must not exceed 20.

Field or button

Description

 Variable types

Branches

The names of the parallel branches. The default branch names are Branch 1 and Branch 2.

Text, Integer

Add branch

Adds another branch.

Important: 

  • The maximum number of branches you can add is 20.

  • If a Run parallel paths action has child Run parallel paths actions, the combined branches of the parent and child Run parallel paths actions must not exceed 20.

 n/a

Removes a branch.

n/a
Completion Condition

Specifies when the Run parallel paths action completes. The completion condition is evaluated once, at the start of the action, using the variable’s value before the branches run. Changes to the variable while the action is running do not affect the completion behavior.

  • True: The action completes as soon as any one branch completes. This does not mean the action waits for the variable to become true.

  • False or not set: The action waits for all branches to complete before continuing.

Changes made to variables within one branch are not visible to sibling branches and do not trigger the completion condition to be evaluated again.

 Boolean