Loading
Salesforce now sends email only from verified domains. Read More
Automate Your Business Processes
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Considerations for Processes in Transactions

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            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.

            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
            Important
            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.

            By default, if one process in a batch fails, it causes all the processes in the batch to fail, and the transaction rolls back. If one process in a batch fails while executing one of these actions, Salesforce attempts to save all successful record changes in the batch up to three times.

            • Create a Record
            • Flows (Create Records and Update Records elements only)
            • Processes (Create a Record and Update Records actions only)
            • Update Records
            Example
            Example When you upload 100 cases, the flow MyProcess_2 triggers one process for each case.
            • 50 processes stop at Create a Record action Create_Task_1.
            • The other 50 processes stop at Create a Record action Create_Task_2.

            The result? At least two groups of bulk operations to execute.

            • One for the 50 processes that execute Create_Task_1
            • One for the 50 processes that execute Create_Task_2
             
            Loading
            Salesforce Help | Article