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. |
- 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!
