You are here:
Schedule-Triggered Flow Considerations
A schedule-triggered flow starts at the specified time and frequency for a batch of records. Understand the considerations and special behaviors of schedule-triggered flows, also known as scheduled flows.
Required Editions
| View supported editions. |
These considerations apply to schedule-triggered flows.
- A schedule-triggered flow starts at the specified time and frequency. You can't start a schedule-triggered flow by any other means.
- The Start Time field value is based on the Salesforce org's default time zone.
- To activate an autolaunched flow that has a trigger, make sure that you have the View All Data permission.
- The maximum number of schedule-triggered flow interviews for a single flow is 250,000.
The maximum number of schedule-triggered flow interviews per 24 hours is 250,000, or the
number of user licenses in your org multiplied by 200, whichever is greater. One interview
is created for each record retrieved by the schedule-triggered flow's query.
- If you specify an object so that the flow runs for a batch of records, set the time, frequency, and record conditions to avoid reaching the limit. A schedule-triggered flow's query retrieves records in batches of 200.
- To check how many records a schedule-triggered flow runs on, use debug logs to track the number of records with the SCHEDULED_FLOW_DETAIL event.
- If your org reaches the limit, Salesforce sends a flow error email.
- If you delete a schedule-triggered flow from the Scheduled Jobs page in Setup, all future recurrences of that flow are canceled. To enable future runs, deactivate and reactivate the flow.
- If a flow is scheduled to run one time with a date and time that has passed, the flow doesn't run.
- The Default Workflow User runs schedule-triggered flows.
- If you need a schedule-triggered flow to run Apex code, don't enable the Require User Access to Apex Classes Invoked by Flow update. If you activate the release update, schedule-triggered flows fail when they run Apex.
- If a schedule-triggered flow meets these criteria, the flow supports callouts without a
Wait element.
- Processes a batch of records
- Runs on API version 63.0 and later
Tip You can insert a Wait element that pauses the flow for only a moment. Configure the resume event to pause until a specified time, with a specific time as the time source. For the base time, specify the$Flow.CurrentDateTimeglobal variable. Then set the offset to 0 hours. At run time, a Wait element that's set up this way typically pauses the flow for less than a minute. - If you configure an Update Records element to use the ID and all field values from the $Record global variable, enable Filter inaccessible fields from flow requests in your org's process automation settings. Otherwise, the flow fails because the Update Records element tries to set the values for system fields and other read-only fields.
- Synchronous Apex transactions invoked by an asynchronous flow contribute to synchronous per-transaction Apex limits. Asynchronous flows include scheduled flows and flows with scheduled or asynchronous paths.
- At run time, if a schedule-triggered flow has a Create Records, Delete Records, Get Records, or Update Records element that processes multiple records and some records fail, all records are rolled back. The successful records are tried again. If the flow has another Create Records, Delete Records, Get Records, or Update Records element later in the flow that processes the same failed records, all changes are rolled back and the flow transaction fails.
- The order of your filter conditions doesn't matter. Salesforce Optimizer evaluates all filters to optimize performance.
- If the Manage Data Export permission is set to Raise
session to high assurance in Session Security Level Policies, you can't activate or deactivate a
schedule-triggered flow in Flow Builder.
- Schedule-triggered flows check the Data Export permission when they're activated or deactivated, regardless of whether the flow uses Scheduled Data Export.
- If this permission requires a high assurance session, you can't activate or deactivate the flow unless you meet the high assurance requirements.
To activate or deactivate the flow, you can either:
- Set Manage Data Export to None in Session Security Level Policies.
- Set Session Security Level Required at Login to High Assurance in the user's profile.
- After a sandbox refresh completes, scheduled flows that were active in the sandbox can run immediately in the refreshed sandbox.
Did this article solve your issue?
Let us know so we can improve!
