Process Limits and Considerations

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

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.

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.

• 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.
• Process Usage-Based Entitlements
  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?
  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
  Before you design a process, understand the limitations and guidelines.
• Considerations for Managing Processes
  Understand what happens when you install, activate, or delete processes.
• Considerations for Deploying Processes
  Keep these considerations in mind when deploying processes, such as when using packages or change sets.
• Considerations for Processes in Transactions
  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.