You are here:
Flow Limits and Considerations
When designing, managing, and running flows, consider the permissions, use limits, and data issues.
Required Editions
| View supported editions. |
Where to Start
Use this roadmap to navigate flow limits and considerations by task. Start with the limits that apply across your org before building, then review design and runtime constraints, and finally consult deployment and packaging considerations when you're ready to distribute.
| Stage | Topic | What You Learn |
|---|---|---|
| 1. Know Your Limits | Flow Usage-Based Entitlements | How interview allocations work, what counts toward your monthly limit, and how additional allocations are granted based on user licenses. |
| General Flow Limits | Org-wide caps on flow versions, active flows, scheduled actions, heap size, and schedule-triggered executions, including separate limits for marketing flows. | |
| Per-Transaction Flow Limits | The Apex governor limits enforced within a single transaction and what happens to the entire transaction when a limit is exceeded. | |
| 2. Design and Build | Flow Builder Considerations | Behavioral limits and quirks of Flow Builder itself, including data access, text formatting, date/time values, variables, permissions, and managed packages. |
| Salesforce Feature Considerations for Flows | How Salesforce platform features—security, external objects, and Lightning components—interact with flows and what constraints apply. | |
| Salesforce Data Considerations for Flows | How to correctly handle record types, person accounts, null values, merge fields, and unsupported field types when flows work with Salesforce data. | |
| Flow Feature Considerations | Constraints specific to flow features such as conditional visibility, default values, variables, paused flows, two-column layout, screen styling, schedule-triggered flows, and record-triggered flows. | |
| MuleSoft for Flow: Integration Limits and Considerations | Constraints for connecting flows to external systems, including general limitations, per-transaction limits, third-party connector specifics, value map behavior, and Agentforce dynamic action restrictions. | |
| 3. Test and Run | Flow Lightning Runtime Considerations | How flows behave at runtime in Lightning Experience, including interview data handling, pause and resume behavior, and display limitations. |
| Flow Builder Debugger Considerations | The limitations and risks of the Flow Builder debug tool, including DML behavior, rollback mode, debugging as another user, and schedule-triggered flow constraints. | |
| 4. Deploy and Distribute | Flow Management Considerations | Rules for activating, deactivating, deleting, and deploying flows, including what happens to in-progress interviews when a new version is activated. |
| Considerations for Packaging Flows | What to include when creating or updating packages that contain flows, and other packaging behaviors such as managed package access and image support. | |
| Change Set Considerations for Flows | What to include in an outbound change set, how flows are deployed as inactive, and the limits around flow triggers in change sets. | |
| Considerations for Flows Installed from Packages | What happens to flow versions, activation status, and in-progress interviews when you install, upgrade, or uninstall a package that contains a flow. |
IN THIS SECTION
- Flow Usage-Based Entitlements
Like feature licenses, usage-based entitlements don’t limit what you can do in Salesforce; they add to your functionality. If your usage exceeds the allowance, Salesforce contacts you to discuss additions to your contract. In the meantime, your flow interviews run as usual. - General Flow Limits
When using flows, keep flow limits and Apex governor limits in mind. - Per-Transaction Flow Limits
Salesforce strictly enforces limits to ensure that any runaway flows don't monopolize shared resources in the multitenant environment. Per-transaction limits, which Apex enforces, govern flows. If an element causes the transaction to exceed governor limits, the system rolls back the entire transaction. The transaction rolls back even if the element has a defined fault connector path. - Flow Builder Considerations
When you create a flow in Flow Builder, familiarize yourself with its limitations and behaviors. For example, Flow Builder supports only a few locales. Because of intellectual property protection, you can’t open flows installed from managed packages, unless the flows are templates. - Salesforce Feature Considerations for Flows
When designing flows, consider these Salesforce features. - Salesforce Data Considerations for Flows
When designing flows, keep these Salesforce data considerations in mind. - Flow Feature Considerations
When designing flows, keep these flow feature considerations in mind. Also, some resources, elements, and screen components have more considerations that are described in their reference topics. - MuleSoft for Flow: Integration Limits & Considerations
When establishing connections to external systems, keep these limitations in mind. - Flow Management Considerations
When managing flows, consider the administration and activation limits. - Considerations for Packaging Flows
You can include a flow in a managed or unmanaged package. Before you create, update, or deploy a package that contains a flow, understand the limitations and behaviors of packages. - Change Set Considerations for Flows
Before you use change sets to deploy a flow, understand the limits and behaviors that are related to component dependencies, deployment, and flow triggers. - Considerations for Flows Installed from Packages
Keep these considerations in mind when you distribute, upgrade, or remove a flow that you installed from a package. - Flow Builder Debugger Considerations
Keep these considerations in mind when using the debug option in Flow Builder.
See Also
Did this article solve your issue?
Let us know so we can improve!
