You are here:
Transactions and Scheduled Actions
Immediate actions in processes are executed in the same transaction as the operation that triggered the process, such as when a user creates or edits a record. Scheduled actions are included in a separate transaction.
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.
Scheduled actions aren’t performed independently. They’re batched in one transaction with other actions that are scheduled to execute at the same time, have the same process version ID, and are executed by the same user ID. This behavior can cause you to exceed your Apex governor limits if the batch’s actions execute DML operations or SOQL queries.
A DML operation is used each time a Salesforce record is created, updated, or deleted, such as when a process executes a Create a Record action. A SOQL query is used each time Salesforce looks up information about an existing record, such as when a process executes an Update Records action. For details on Apex governor limits, see Process Limits.
To improve performance further and help avoid Apex governor limits, design scheduled actions to take advantage of bulkification.
If a process has more than one group of scheduled actions and a group fails to execute in a batch:
- Prior groups of scheduled actions in that batch’s transaction are successful.
- The immediate actions for that process are successful.
- All scheduled actions in that group aren’t executed.
- Each remaining group of scheduled actions in that batch is executed in a separate transaction.
