Do the following in parallel flow logic
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Create Workflows
Run actions and subflows in separate paths within an isolated flow logic block.
With this flow logic, you can run actions and subflows in separate paths. If any action within the Do the following in parallel flow logic block must wait, other actions run until all paths within the block finish processing.

Inputs
Do the following in parallel flow logic does not have field inputs. Instead, it displays a plus () icon that enables you to create a path with actions or subflows.
The actions and subflows in each path run until all tasks within the flow logic block have completed.
Outputs
This flow logic has no outputs, but actions and subflows in each path may have outputs. While the flow is running, outputs from a path are only accessible to other actions in the same path. After the Do the following in parallel flow logic completes, its final outputs are accessible to the rest of the flow.
Example: Create two tasks in parallel when a change request is created
In this example, a flow triggers when a new change request is created. Using Do the following in Parallel, two tasks are created in separate paths and are assigned to different groups. The flow uses the Number field data pill from the triggering change request to display the number in the short description for the task record.

Execution details

- The header shows the state, start time, and runtime for the flow logic.
- The Configuration Details section shows the state, start time, and runtime for each path in the flow logic block.
General guidelines
- Avoid creating data dependencies between paths
- Since a flow can run paths in any order, avoid creating data dependencies between separate paths. For example, do not have one path that creates a record and another path that updates the same record. The update record path may run before the create record path.
- Do not share data between paths
- Workflow Studio prevents you from dragging data pills between paths because the system cannot determine which path will finish first to supply the output value.
On this page
Related Content
- Assign subflow outputs flow logic
Specify the data the subflow returns when it completes running. Use subflow output as data for a parent flow or as input for another process.
- Call a workflow flow logic
Run a published and active workflow from your flow. You can use the flow data as a workflow input. For example, you can specify the current record as a workflow input.
- Do the following until flow logic
Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.
- Dynamic flows flow logic
Identify and run a flow or subflow dynamically by using runtime data. Build templates to provide expected inputs for dynamically called flows or subflows.
- End Flow flow logic
Stop running the current flow. Use End Flow within a branch of the flow to specify an exit condition. For example, end the flow when it reaches a specific If flow logic block.
- Exit Loop flow logic
Exit from a flow logic loop when the conditions of an If flow logic are met. Continue running the flow from the next step after the flow logic loop. This flow logic is also known as break.
- For Each flow logic
Apply one or more actions to each record in a list of records.
- Go back to flow logic
Return to a prior step in the flow to repeat a sequence of actions.
- If flow logic
Selectively apply one or more actions only when a list of conditions is met.
- Make a decision flow logic
You can use the decision table branching logic in situations where multiple conditional paths are required, as an alternative to nested If, Else If, or Else flow logic. For example, if you want to determine what kind of car insurance you need, you can add inputs such as your age, accident history, and car model to the decision table to determine a level of insurance coverage. This logic can save you time and present a more readable format than nested if conditions or switch case statements.
- Set Flow Variables flow logic
Assign a value to one or more flow variables, which store flow data as data pills. Access flow variable values by referring to their data pill.
- Skip Iteration flow logic
Skip the current iteration of a flow logic loop when the conditions of an If flow logic are met. Continue running the flow logic loop with the next item in the list. This flow logic is also known as continue.
- Try flow logic
Allow a flow to continue running when an error occurs within a flow logic block. Run a sequence of actions in response to errors within the flow logic block.
- Wait for a duration flow logic
Use this flow logic to give your users time to act during automated processes or to wait for a specific date and time to complete actions.