---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# For Each flow logic

# For Each flow logic {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of For Each flow logic

The For Each flow logic in ServiceNow allows you to apply one or more actions to each record within a list sequentially.
It processes each item individually, enabling granular handling of records in workflows.
This flow logic is particularly useful for scenarios like sending notifications or updating multiple records based on a list generated dynamically.
Show full answer Show less  
**Important:** Data pill values set inside a For Each branch are only accessible within that branch and cannot be referenced outside it. Processing large lists can be resource-intensive, so performance optimization may be necessary.

## Inputs and Outputs

* **Inputs:** Accepts a list of records or Sys ID values, typically produced by actions like Look Up Records. You can sort these records beforehand if processing order matters.
* **Outputs:** Provides the current record in the loop as a data pill, which can be used by subsequent actions within the loop branch.

## Performance Considerations

* Avoid processing lists larger than 1000 records in a single For Each loop to maintain optimal flow performance.
* For larger datasets, split the list into smaller batches and use multiple flows.
* Disable reporting via the `com.snc.processflow.reporting.level` system property to reduce overhead when iterating over many records.

## General Guidelines

* Do not place stages inside a For Each block; stages can only be added before or after the block.
* Avoid nesting For Each loops that process many records to prevent exceeding flow transaction quotas (flows running longer than one hour).

## Example Use Case

An example flow triggers when a change request is created. It uses a Look Up Records action to find Configuration Items related to the requester and then applies a For Each loop to send emails about each potentially affected Configuration Item. The flow execution details track each configuration item processed in the loop.

## Additional Resources

For comprehensive flow design, consider related flow logic such as Assign subflow outputs, Call a workflow, Do the following until, If flow logic, and more to build complex and efficient workflows.  
Apply one or more actions to each record in a list of records.  
The For Each flow logic applies one or more actions to a list of records. The flow applies the actions contained within the flow logic to each record in the list.  
Note:  
When you set a data pill value from inside a For each item branch of flow logic, the data pill value is only available to other actions in the same branch. Referencing a data pill value that was set inside a For each branch from outside of the flow logic branch produces a null value.

Iterating over a large number of records can be resource intensive, especially when the For Each logic block includes complex actions for each iteration. To avoid performance issues, turn off reporting using the com.snc.process_flow.reporting.level system property. For more information, see [Workflow Studio flow system properties](https://www.servicenow.com/docs/7WoJMrXB9sTBbYgH1yjP0Q "Configure how the system processes flows.").

## Inputs {#flow-logic-for-each__section_tyr_cxk_r2b}

Items
    : Data type: Records  
    List of Sys ID values or Records data pill specifying the records to process in sequence. You can use a Look Up Records action to generate a list of records. For more information, see [Look Up Records action](https://www.servicenow.com/docs/T1aQhPS6vFM8iocC6Pxizg "Look up multiple records on any table using defined conditions.").  
    Note:  
    If you want to process items in a particular order, you must first sort the items in this input in advance. For example, use the Order by option to sort the results of a Look Up Records action.

## Outputs {#flow-logic-for-each__section_vxs_gzk_r2b}

\[Table name\] Record
:   Data type: Record  
    Current record in the loop.  
    Note:  
By default, all flow loops only store execution details for the first and last iterations of a loop. To report on all iterations of a loop, create a flow execution setting record for each flow that you want to collect loop execution details. For more information about flow execution settings, see [Flow execution settings](https://www.servicenow.com/docs/eeDwCkiqfR09saPnBUWSUw "Specify the runtime settings for an individual flow, subflow, or action such as the run priority, reporting level, and logging level.").  

## Send an email for each configuration item potentially affected by a change

This example flow starts when a change request record is created. The flow uses a Look Up Records action to find Configuration Item records assigned to the requester of the change request. The flow uses For Each flow logic to
send an email about each configuration that might be affected by the change request. The output of the Look Up Records action contains the list of records to process.

The flow execution details show the configuration item record used for each iteration of the loop.

## General guidelines {#flow-logic-for-each__section_vkq_bcs_tbc}

Use these general guidelines with a For Each flow logic.

Avoid adding more than 1000 items
:   Avoid iterating over lists with more than 1000 records. Keep your list of records smaller to optimize flow performance. To iterate over lists with more than 1000 records, divide the list into smaller sections and use
    multiple flows.

Avoid defining stages that depend on a For Each flow logic
:   Flow Designer prevents you from adding stages within a For Each block. You can only add stages before or after a For Each block.

Avoid nested For Each loops
:   Avoid nested For Each loops that process many records. Nested loops may cause the flow to run until it is stopped by the flow transaction quota rule, which prevents flows from running longer than an hour. For more
    information about transaction quotas, see [Transaction quotas](https://www.servicenow.com/docs/access?context=c_TransactionQuotas&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).
**Related concepts**   

* [Assign subflow outputs flow logic](https://www.servicenow.com/docs/BPYImTV9HJoIPPnwGPh~fg "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](https://www.servicenow.com/docs/qZcmPZCegzFAHnd31j7heA "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](https://www.servicenow.com/docs/eSbS7MMbSBu30a8dSjMBng "Apply one or more actions repeatedly until an end condition is met. You can use the flow data to specify the end conditions.")
* [Do the following in parallel flow logic](https://www.servicenow.com/docs/7PJmWFojwFDIqu9dkF7_lw "Run actions and subflows in separate paths within an isolated flow logic block.")
* [Dynamic flows flow logic](https://www.servicenow.com/docs/ubno_xW91uUeFZuVIQaySg "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](https://www.servicenow.com/docs/Sp7jPg4NNYSwqRP8XOZouA "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.")
* [If flow logic](https://www.servicenow.com/docs/TjnRtaiEgKxX4PD0DUqfcA "Selectively apply one or more actions only when a list of conditions is met.")
* [Make a decision flow logic](https://www.servicenow.com/docs/Jglm9N3IKaFJ1mfoX8SX3Q "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](https://www.servicenow.com/docs/~PbDvIgeB82CFqu~11nGvQ "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.")
* [Try flow logic](https://www.servicenow.com/docs/bmLWueso8VCOr_035PJQKg "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](https://www.servicenow.com/docs/ucONIbAnUeCKaCUOpk~Hlw "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.")  
**Related reference**   

* [Exit Loop flow logic](https://www.servicenow.com/docs/9FuSmMLS5Ub2t8ypV_xJOQ "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.")
* [Get Flow Outputs flow logic](https://www.servicenow.com/docs/AmvE1SZ0P8d_clYXtrrUgw "Retrieve output values generated by dynamic flows or subflows.")
* [Go back to flow logic](https://www.servicenow.com/docs/bhUS9xEo2lNvyY9~JY5mqA "Return to a prior step in the flow to repeat a sequence of actions.")
* [Skip Iteration flow logic](https://www.servicenow.com/docs/F2ltfoIaBnP~iH3UFz9hiw "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.")