---
schema_version: "1"
id: 40a7370d0ef3a08f3aa9683063901227aad6812d81f994f01388c40b8738dc05
title: Process Limits and Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bc3926278775e3cb38868fd76a23a2086d9103d1f739923d59d3d533ff412115
description: Before you start creating, managing, and activating processes, understand the limits and considerations.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Process Limits and Considerations

Before you start creating, managing, and activating processes, understand the limits and considerations.

![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.").

- **[Process Limits](https://help.salesforce.com/s/articleView?id=platform.process_limits.htm&release=264.0.0&type=5)**  
    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.
- **[Process Usage-Based Entitlements](https://help.salesforce.com/s/articleView?id=platform.process_usage_entitlements.htm&release=264.0.0&type=5)**  
    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 processes continue to run as usual.
- **[When Do Processes Evaluate Record Changes?](https://help.salesforce.com/s/articleView?id=platform.process_considerations_works.htm&release=264.0.0&type=5)**  
    Processes start automatically and are invisible to the user. Before you design or activate a process, understand which changes trigger processes.
- **[Considerations for Designing Processes](https://help.salesforce.com/s/articleView?id=platform.process_considerations_design.htm&release=264.0.0&type=5)**  
    Before you design a process, understand the limitations and guidelines.
- **[Considerations for Managing Processes](https://help.salesforce.com/s/articleView?id=platform.process_considerations_activation.htm&release=264.0.0&type=5)**  
    Understand what happens when you install, activate, or delete processes.
- **[Considerations for Deploying Processes](https://help.salesforce.com/s/articleView?id=platform.process_changesets_packaging.htm&release=264.0.0&type=5)**  
    Keep these considerations in mind when deploying processes, such as when using packages or change sets.
- **[Considerations for Processes in Transactions](https://help.salesforce.com/s/articleView?id=platform.process_considerations_transactions.htm&release=264.0.0&type=5)**  
    Each process runs in the context of a transaction. A transaction represents a set of operations that are executed as a single unit. When a process is triggered more than one time in a single transaction, Salesforce executes similar actions in one batch.