You are here:
Process Limits
When building processes, keep shared limits and Apex governor limits in mind. In addition, a process’s API name must be unique across all processes and flows in your Salesforce org.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.
Limits Shared with Other Features
Processes share some limits with rules and flows.
| Per-Org Limit | Essentials or Professional Edition | Enterprise, Unlimited, Performance, or Developer Edition |
|---|---|---|
Active record change processes and rules per object Rules include workflow rules, escalation rules, assignment rules, and auto-assignment rules. |
50 | 50 |
| Total processes | 5 per process type | 4,000 per process type |
| Active processes | 5 per process type | 2,000 per process type |
| Criteria nodes that are evaluated and actions that are executed at runtime per process | None 1 | None 1 |
| Groups of scheduled actions that are executed or flow interviews that are resumed per hour | 1,000 | 1,000 |
Combined total of these automations that start or resume based on a record’s field value.
|
20,000 | 20,000 |
The daily limit for emails sent from email alerts is 1,000 per standard Salesforce license per org, except for Developer Edition orgs. For a Developer Edition org, the daily workflow email limit is 15 per standard Salesforce license. The overall org limit is 2,000,000, which is shared across all features that use workflow email alerts: workflow rules, approval processes, flows, and processes.
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.
Apex Governors and Limits for Processes
Salesforce strictly enforces limits to ensure that runaway processes don’t monopolize shared resources in the multitenant environment. Processes are governed by the per-transaction limits that are enforced by Apex. If a process launches other automation in the same transaction, that automation shares the process transaction’s limits. If the process or its launched automation causes the transaction to exceed governor limits, the system rolls back the entire transaction. For details about the operations that are included in the transaction, see Triggers and Order of Execution in the Apex Developer Guide.
| Description | Per-Transaction Limit |
|---|---|
| Total number of SOQL queries issued | 100 |
| Total number of records retrieved by SOQL queries | 50,000 |
| Total number of DML statements issued | 150 |
| Total number of records processed as a result of DML statements | 10,000 |
| Maximum CPU time on the Salesforce servers | 10,000 milliseconds |
Each Create a Record action uses one DML statement. Each Quick Action action uses one DML statement. Each Update Records action uses one SOQL query and one DML statement. Each Flows action can use multiple SOQL queries and DML statements, depending on the elements that the flow executes. For details, see Per-Transaction Flow Limits.
Limits for Creating and Managing Processes
Consider these limits when creating and managing processes.
| Per-Process Limit | Value |
|---|---|
| Total characters in a process name | 255 |
| Total characters in a process’s API name | 79 |
| Total versions of a process | 50 |
| Total criteria nodes in a process | 200 |
