Salesforce
FLOW
limitations
Salesforce Flows are a powerful tool for
automating tasks and building custom
processes in your org. But like everything
else, they come with certain limits.
Understanding these limits can help you
avoid errors and ensure your flows run
smoothly.
In this guide, we’ll walk through the key
flow limits and share practical strategies
to help you optimize your flows and stay
within those constraints.
@salesforcegeek swipe
Total SOQL Queries Per Transaction - 100
This limit controls how many times a flow can
fetch data using SOQL in a single transaction.
SOQL queries help retrieve information from
Salesforce objects.
Here’s how you can avoid hitting this limit:
Break down large flows into smaller, more
manageable ones.
Use filters in your SOQL queries to fetch only
the necessary data, reducing the load.
@salesforcegeek swipe
Total DML Statements per Transaction - 150
This limit controls how many times a flow can
create, update or delete records (DML operations)
in a single transaction.
If your flow handles a large amount of data, like
creating multiple records or updating them in
bulk, it can quickly hit this limit.
To avoid this:
Optimize data handling by reducing the
number of records processed at once.
Process records in smaller batches to stay
within the limit.
@salesforcegeek swipe
Total Records Retrieved by SOQL Queries
A flow can retrieve up to 50,000 records across all
SOQL queries in a single transaction. This limit
helps prevent system overload from large
datasets.
If your flow pulls in too much data, especially
without proper filters. It can quickly reach this cap.
To stay within limits:
Use filters in SOQL queries to fetch only the
necessary records.
Retrieve only relevant data to keep the flow
efficient and avoid hitting the limit.
@salesforcegeek swipe
Total Number of Records Processed by DML
A flow can process up to 10,000 records using DML
operations (create, update, delete) in a single
transaction. This limit helps maintain data
integrity and system performance.
If your flow needs to handle a large volume of
records:
Consider using asynchronous flows, which
process data in stages to manage large updates
more efficiently.
Break down record processing to stay within
the limit and ensure smooth execution.
@salesforcegeek swipe
Maximum CPU Time on the Salesforce
Servers
Salesforce allows a maximum of 10 seconds
(10,000 milliseconds) of CPU processing time per
transaction. This ensures the system runs
efficiently without overloading the servers.
To avoid hitting this limit:
Optimize your flow’s logic to reduce
processing time.
Minimize complex operations and
unnecessary loops to keep execution smooth.
@salesforcegeek swipe
Maximum Number of Executed Elements
at Runtime per Flow
With API Version 57.0 and beyond, the
2,000 flow element limit has been removed!
In earlier versions (56.0 and before), flows
were restricted to 2,000 elements, but now
you can build more complex flows without
worrying about this cap.
@salesforcegeek swipe
FOUND
THIS INSIGHTFUL?
Feel free to like, share and comment
