---
title: "Branch ForEach Step"
slug: "branch-foreach-step"
tags: ["branch", "ForEach", "collection"]
updated: 2023-01-11T15:10:23Z
published: 2023-01-11T15:10:24Z
canonical: "documentation.decisions.com/branch-foreach-step"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Branch ForEach Step

| ## Step Details |
| --- |
| **Introduced in Version** | --- |
| **Modified in Version** | --- |
| **Location** | Flow Management > Branching |

The **Branch ForEach** step iterates through every item in an input Collection and passes them to one or more steps. This step is similar to the standard [**ForEach**](https://documentation.decisions.com/step-library/docs/foreach-step) step, with two key differences:

- It branches the Flow into multiple paths
- The Flows following a Branching ForEach step do not need to complete the loop by forming a return path to the Branching ForEach step. The control of the Flow returns to the Branching ForEach step at the Flow's end automatically.

This can be useful for [**Parallel** **Approval**](/v8/docs/branching-and-merging-flows) processes that involve the iteration and [**Assignment**](https://documentation.decisions.com/v8/docs/about-assignments) of multiple pieces of data, i.e., displaying individual retrieved **Account** data on a **Form**. The following document demonstrates how to utilize a Branching ForEach step in for such use cases.

This step is meant to be exclusively used with Assigned Forms and is not meant for Batch Processing. 

---

## Properties

#### Collection

| Property | Description | Data Type |
| --- | --- | --- |
| Type | Allows a user to select a data type | --- |
| Fail If Empty | Creates an outcome path for an empty value | Boolean |

#### Inputs

| Property | Description | Data Type |
| --- | --- | --- |
| Collection | List of the specified Data Types | List of [DataType] |

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1666624923539.png)

---

## Common Errors

Using a Sub Flow between the Branch ForEach and Merge Step is a required configuration. Failure to utilize one will cause the Flow Designer to throw a Validation Warning. Thus, any Form following a Branch ForEach must be run via Sub Flow.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2023-01-11_10h09_19.png)

Related Information

Forum Posts: [Using Branch For Each Step And Getting Errors](https://support.decisions.com/forum/topic56-using-branch-for-each-step-and-getting-errors.aspx) [Running Branch For Each Step Asynchronously](https://support.decisions.com/forum/topic1975-running-branch-for-each-step-asynchronously.aspx)

## Related

- [ForEach Step](/foreach-step.md)
- [ForEach in Group Step](/foreach-in-group-step.md)
- [Reset For Each Step](/reset-step.md)