--- schema_version: "1" id: 71475317474930d261a340d990ea8eca143e6d5c62a95c65ebbbd90f1d0ede3e title: Flow Limits per Org collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_considerations_limit.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_considerations_limit.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 165c1f8f40ac633423d00c9ee8e5cbc51773ad197684098c4a52da32163621fc description: Review per-org, per-interview, and marketing flow limits, including limits for flow versions, active flows, scheduled interviews, and heap size. products: - Flow Builder - Salesforce Platform release: "264" --- # Flow Limits per Org Review per-org, per-interview, and marketing flow limits, including limits for flow versions, active flows, scheduled interviews, and heap size. ### Required Editions
View supported editions.
## General Flow Limits The maximum flow interview size is approximately 1 MB. If the interview is too large, it can't be persisted or paused.
Per-Org Limit Essentials or Professional Editions Enterprise, Unlimited, Performance, or Developer Editions
Versions per flow 50 50
Elements run at runtime per flow None None 1
Active flows per flow type2 5 2,000
Total flows per flow type2 5 4,000
Groups of scheduled actions from processes that are run per hour based on a specific time 1,000 1,000

Combined total of these automations that start or resume based on a record’s field value.

  • Resume events that are defined in active flows
  • Groups of scheduled actions that are defined in active processes
  • Time triggers that are defined in active workflow rules
  • Inactive flow interviews that are resumed
 20,000 20,000
Schedule-triggered flow interviews per 24 hours 250,000, or the number of user licenses in your org multiplied by 200, whichever is greater.3
Total heap size per flow interview 215 MB4
1In API version 57.0, the limit of 2000 flow elements was removed. In API version 56.0 and earlier, flows could have a maximum of 2000 flow elements. 2These limits don't apply to marketing flows. See the [Limits for Marketing Flows](https://help.salesforce.com/s/articleView?id=platform.flow_considerations_limit.htm&release=264.0.0&type=5) section for more information. 3The license types that count toward this limit include: full Salesforce and Salesforce Platform user licenses, App Subscription user licenses, Chatter Only users, Identity users, and Company Communities users. 4In API version 61.0, the limit was changed to 215 MB. In API version 60.0 and earlier, the limit is 750 MB. Salesforce doesn’t report flow heap usage for this limit. The heap usage shown in Apex debug logs is for Apex governor limits, not for this flow limit. Make sure to also review per-transaction limits, such as how many Create Records elements you can have, in [Per-Transaction Flow Limits](https://help.salesforce.com/s/articleView?id=platform.flow_considerations_limit_transaction.htm&release=264.0.0&type=5 "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."). ## Limits for Marketing Flows These limits apply to segment-triggered flows, form-triggered flows, automation event-triggered flows, activation-triggered flows, on-demand flows, and broadcast flows, depending on Marketing Cloud edition. | Per-Org Limit | Marketing Cloud Starter Edition | Marketing Cloud Growth Edition, or Data 360 | Marketing Cloud Advanced Edition | | --- | --- | --- | --- | | Active flows per flow type | 50 | 500 | 750 | | Active automation event-triggered flows per trigger object1 | Not applicable | 20 | 30 | | Total flows per flow type | 2,000 | 50,000 | 50,000 | 1Automation event-triggered flows have a per-trigger-object limit that applies separately to each object, such as Lead, Contact, or Prospect. This limit is separate from the org-wide active flows allocation. When you reach the limit for a trigger object, deactivate an active automation event-triggered flow for that object before you activate another one. Segment-triggered flows, form-triggered flows, automation event-triggered flows, activation-triggered flows, on-demand flows, and broadcast flows bulkify certain operations, grouping together up to 200 record changes per transaction. For more information on bulkification, see [Flow Bulkification in Transactions](https://help.salesforce.com/s/articleView?id=platform.flow_concepts_bulkification.htm&release=264.0.0&type=5 "When a flow runs for multiple records at the same time, Salesforce creates one flow interview per record. Bulkification groups similar operations when interviews for the same flow reach the same element, helping the transaction use fewer queries and statements."). Elements that can trigger bulkified operations include: - Create Records - Get Records - Update Records - Delete Records - Subflows - Apex Actions - Flow Core Actions #### See Also - [Automate Tasks with Flows](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.") - [Flow Limits and Considerations](https://help.salesforce.com/s/articleView?id=platform.flow_considerations.htm&release=264.0.0&type=5 "When designing, managing, and running flows, consider the permissions, use limits, and data issues.")