Schedule-Triggered Flow (or Scheduled Flow) is a Salesforce Flow that launches automatically and repeats itself at certain intervals.
For a batch of records, a schedule-triggered flow begins at the appointed time and frequency.
By using Schedule-Triggered Flow, you can totally drop the idea to use the Apex Schedule Jobs by using Batch Apex.
They are also known as Scheduled Flows because of their unusual behavior and the conditions provided by them.
You can set this Flow to run at a specific time at:
- Daily or
Don't forget to check out: Know About Flows in Salesforce - Learn Here
These considerations apply to Schedule-triggered Flows:
- At the time and frequency set by the schedule, a flow begins. There is no other way to start a schedule-triggered flow.
- The Start Time field value is based on the Salesforce org’s default time zone.
- An auto-launched flow with a trigger can only be activated if the user has View All Data access.
- The number of schedule-triggered flow interviews that can be conducted in a 24-hour period is limited to 250,000, or the sum of your organization's user licenses times 200, whichever is higher. Each record obtained by the schedule-triggered flow's query is the subject of one interview.
- Set the time, frequency, and record conditions if you specify an object so that the flow runs for a batch of records in order to stay within this limit. To determine how many forms a schedule-triggered flow executes on, see debug logs. Use the FLOW_START_SCHEDULED_RECORDS event to keep track of the number of records. A flow error email is sent by Salesforce if your organization exceeds the limit.
Check out another amazing blog by Sejal here: What is the Custom Metadata Type in Salesforce in 2023?
- All subsequent occurrences of a schedule-triggered flow are stopped if the flow is deleted from the Scheduled Jobs page in Setup. Deactivate and then reactivate the flow to allow future runs.
- A flow doesn't run if it is planned to run once at a time and date that have passed.
- Schedule-triggered flows are executed by the Automated Process user.
- Do not enable the Require User Access to Apex Classes Invoked by Flow update if you require a schedule-triggered flow to execute Apex code. Schedule-triggered flows that attempt to execute Apex when that release update is active fail.
- Callouts can only be made by a schedule-triggered flow after a Pause element has been executed. Without a Pause element, the flow, for instance, is unable to access external objects, run Apex actions that create callouts, or run actions that are derived from registrations for External Services.
- Enable Filter inaccessible fields from flow requests in your org's process automation settings if you set up an Update Records element to use the ID and all field values from the $Record global variable. If the Update Records element tries to set the values for system fields and other read-only fields, the flow will fail.
- The default filter logic when you define several filters is often AND. The filters are combined with OR if more than one filter has the same field selected and uses the equals operator.