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