---
schema_version: "1"
id: b1269beaaa753751963f411b4f949515e84fc43ae241b897be134b84104de371
title: Transactions and Scheduled Actions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_limits_scheduled_transactions.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_limits_scheduled_transactions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e1337a96e33665903bffd2c3eaf2d27b9a8ac1dc94668887a65f484b2bbc59e5
description: 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.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (<a href="https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&amp;language=en_US" target="_blank">not available in all orgs</a>) and Lightning Experience</td></tr><tr class="" id="process_limits_scheduled_transactions__d3881e343"><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <span id="process_limits_scheduled_transactions__d3881e347"><a name="process_limits_scheduled_transactions__d3881e347"></a><strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</span></td></tr></tbody></table>

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

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](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.").

To improve performance further and help avoid Apex governor limits, design scheduled actions to take advantage of bulkification.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png)

Tip Design a process with a scheduled action so that it doesn’t execute mixed DML operations. A single transaction can’t mix DML operations on data objects (such as Account), Setup objects (such as User Role), and external objects. For example, you can’t update an account and a user role in a single transaction.

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.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_example.png)

Example Salesforce processes two groups of scheduled actions in the same batch. In the first group, one action fails, so the process fails. Subsequent actions within the first group aren't tried. Salesforce processes the second group in a separate transaction.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note The execution time is now in the past, so Salesforce executes the second group of scheduled actions within 1 hour.