---
schema_version: "1"
id: cebb061271e1a6489dacd5715345abc00f3e79efee7ad3f1c9d39f1fb2b38a78
title: Process Limits
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_limits.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_limits.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1e8581f9d3bc685bbd4f82b883f72a65e23e365f62d124f8525f5f61dc53dde8
description: 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.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_limits__d3087e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_limits__d3087e347"><a name="process_limits__d3087e347"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).

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](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](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.").

## Limits Shared with Other Features

Processes share some limits with rules and flows.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:66.66666666666666%">
          <col style="width:16.666666666666664%">
          <col style="width:16.666666666666664%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:middle;" id="d86493e125">Per-Org Limit</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d86493e128">Essentials or Professional Edition</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d86493e131">Enterprise, Unlimited, Performance, or Developer Edition</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">
              <p>Active record change processes and rules per object</p>
              <p style="margin-bottom:0;">Rules include workflow
                rules, escalation rules, assignment rules, and auto-assignment rules.</p>
            </td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 ">50</td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 ">50</td>

          </tr>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">Total processes</td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 "><span>5</span> per process type</td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 "><span>4,000</span> per process type</td>

          </tr>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">Active processes</td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 "><span>5</span> per process type</td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 "><span>2,000</span> per process type</td>

          </tr>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">Criteria nodes that are evaluated and actions that are executed at runtime per
              process</td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 ">
              <span>None</span>
              <sup>1</sup>
            </td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 ">
              <span>None</span>
              <sup>1</sup>
            </td>

          </tr>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">Groups of scheduled actions that are executed or flow interviews that are
              resumed per hour</td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 ">
              <span>1,000</span>
            </td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 ">
              <span>1,000</span>
            </td>

          </tr>
          <tr class="">
            <td data-label="Per-Org Limit" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e125 ">
              <p>Combined total of these automations that start or resume based on a record’s
                field value.</p>
              <ul>
                <li>Resume events that are defined in active flows</li>
                <li>Groups of scheduled actions that are defined in active processes</li>
                <li>Time triggers that are defined in active workflow rules</li>
                <li>Inactive flow interviews that are resumed</li>
              </ul>
            </td>

            <td data-label="Essentials or Professional Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e128 ">
              <span>20,000</span>
            </td>

            <td data-label="Enterprise, Unlimited, Performance, or Developer Edition" class="slds-cell-wrap" style="vertical-align:top;" headers="d86493e131 ">
              <span>20,000</span>
            </td>

          </tr>
        </tbody>
      </table>

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](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 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 |