Salesforce Developer Limits Quick Reference
jNewer Version Available
Process Limits
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
Limits Shared with Other Features
Processes share some limits with rules and flows.
In addition to the following limits, a process’s API name must be unique across all processes and flows in your org.
| Description | Per-Org Limit |
|---|---|
| Total number of active rules and active processes per object Rules include workflow rules, escalation rules, assignment rules, and auto-assignment rules. Invocable processes don’t count toward this limit. |
50 |
| Total number of flows and processes | 1,000 |
| Total number of active flows and processes | 500 |
| Total number of criteria nodes that are evaluated and actions that are executed at runtime | 2,000 |
| Total number of flow interviews that are resumed or groups of scheduled actions that are executed per hour | 1,000 |
| Total number of flow interviews or groups of scheduled actions that are waiting to be processed | 30,000 |
| Total number of relative time alarms defined in flow versions or schedules based on a field value in processes | 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.
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 the process 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 |
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 Limits for Visual Workflow.
Limits for Creating and Managing Processes
Consider these limits when creating and managing processes.
| Description | Limit |
|---|---|
| Total number of characters in a process name | 255 |
| Total number of characters in a process’s API name | 77 |
| Total number of versions of a process | 50 |
| Total number of criteria nodes in a process | 200 |