In one Salesforce transaction, the current Flow limits include 100 SOQL queries and 150 DML statements. Those allowances are shared by the work in that transaction—not granted separately to every flow interview—and other automation or Apex can use part of them. SOQL rows, DML-processed records, and server CPU time have separate ceilings.
Salesforce Flow limits at a glance
Salesforce’s Per-Transaction Flow Limits page lists these limits for a transaction. The documentation does not display a publication year for the table.
| Limit | Per-transaction allowance | What counts |
|---|---|---|
| SOQL queries | 100 | Get Records executions; Update Records and Delete Records executions when they use filter conditions. |
| Records retrieved by SOQL | 50,000 | Rows retrieved through SOQL. |
| DML statements | 150 | Create Records, Update Records, and Delete Records executions. |
| Records processed by DML | 10,000 | Records affected as a result of DML statements. |
| Salesforce server CPU time | 10,000 milliseconds | CPU time used in the transaction. |
| Duplicate updates | 12 in one batch | Duplicate updates allowed in a batch. |
For the short interview answer: 100 queries, 150 DML statements, 50,000 SOQL-retrieved records, 10,000 DML-processed records, and 10 seconds of server CPU time per transaction. These are distinct limits; staying below one does not mean the others are available or unaffected.
Do Flow interviews share governor limits?
Yes, when they run in the same transaction. A flow interview is one running instance of a flow; a transaction is the unit of work whose operations share governor limits and commit or roll back together. The two terms are not interchangeable.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
- SALESFORCE CERTIFIED ADMINISTRATOR RAPID CERTIFICATION EXAM PREP GUIDE: Quick Prep for Certification Exam Guide for Salesforce Admin Certification with questions and practice tests
- ABIS BOOK
- Independently published
Autolaunched flows
An autolaunched flow participates in the transaction that launched it. If Apex, a process, or other work starts the flow, that launching work and other operations in the transaction can consume the same limits. One interview therefore does not come with a fresh pool of 100 queries or 150 DML statements. See Salesforce’s How Flows Run in Transactions.
Screen flows and waits
A Screen, Local Action, or Wait element ends the existing transaction and starts a new one. A Wait pauses the interview; when it resumes, work after the Wait runs in a new batch transaction. That batch can include other resumed interviews with the same user ID, execution time, and flow version ID.
Rank #2
Do not add a screen or wait merely to reset limits: transaction boundaries affect how the flow executes and should be part of its design. Salesforce suggests considering a boundary when a flow is likely to hit a governor limit within its transaction.
How Get Records, updates, and deletes use limits
Get Records and SOQL
Get Records uses SOQL, so each execution counts toward the transaction’s query limit, and the rows it retrieves count toward the separate 50,000-record SOQL ceiling.
Update Records and Delete Records
Update Records and Delete Records perform DML and count toward the 150-statement limit. When either element uses filter conditions, its execution also counts toward the SOQL query limit.
Create Records
Create Records executions count as DML. The records processed by DML statements are measured separately from the number of statements, so a single bulk operation can affect many records while consuming a statement and adding those records to the DML-processed total.
What bulkification changes—and what it does not
When Salesforce processes a bulk run, it creates one flow interview per record. Bulkification can group similar operations when interviews for the same flow reach the same element, reducing the number of separate queries or DML statements. It does not give each interview an independent limit allowance: the grouped operations still consume limits in their transaction.
To reduce repeated work, avoid placing data operations inside loops when an operation can instead act on a collection. Also account for other flows, Apex, triggers, and automation running in the same transaction; the Flow’s visible elements may not be the only consumers of queries, DML, or CPU.
What happens if a Flow exceeds a governor limit?
Salesforce states: “If an element causes the transaction to exceed governor limits, the system rolls back the entire transaction.” This applies even if the element has a defined fault connector. A fault path does not make a governor-limit exception safe or prevent the rollback.
How to troubleshoot a query or DML limit error
- Establish the transaction boundary. Determine what launched the flow and whether a Screen, Local Action, or Wait begins a new transaction. Identify other work that shares the transaction.
- Find repeated operations. Review Get Records and record-update or delete logic, especially data operations inside loops that could be replaced with collection-based work.
- Inspect related automation. Check which flows, Apex, triggers, and other automation run in the same transaction and contribute queries, DML, or CPU use.
- Review available run data. Salesforce documents flow run and element analytics, on-canvas element run data, screen-flow reports, and persistent logging options. Availability and setup depend on flow type and org configuration; see Managing and Monitoring Flows.
How transaction limits differ from other Flow limits
Per-transaction governor limits are not the same as per-interview or org-wide capacity limits. Reaching the transaction limits can roll back the transaction; an oversized interview cannot be persisted or paused; and org-level caps restrict capacity based on the org or flow type.
Per-interview and org-wide examples
Salesforce’s Flow Limits per Org page lists an approximate 1 MB maximum interview size and 50 versions per flow. The page also lists a total heap size of 215 MB per flow interview. Salesforce says this heap limit changed to 215 MB in API version 61.0; API version 60.0 and earlier used 750 MB. Flow heap usage is not reported, and Apex debug-log heap figures refer to Apex governor limits, not this separate Flow limit.
The same page gives a daily schedule-triggered interview limit of 250,000 or 200 times the number of eligible user licenses, whichever is greater. Active-flow and total-flow caps vary by edition; marketing flows have separate edition-specific limits. Check the current Salesforce page for the applicable org and flow type rather than treating those capacity limits as transaction allowances.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
