The current way to build a scheduled action is a scheduled path inside an after-save record-triggered flow. The steps below assume Flow Builder and an object that already has a date or date/time field to anchor the timing.
- Create an after-save record-triggered flow
In Setup, open Flow Builder and create a Record-Triggered Flow. Choose the object, set the trigger (created, updated, or created or updated), and pick the Actions and Related Records option so the flow runs after save. Scheduled paths are not available on before-save flows.
- Add a scheduled path
On the Start element, add a Scheduled Path. Give it a label, then define the timing with a Time Source (a field like Close Date or the record creation time), an Offset Number, and an Offset Option such as Days After or Hours Before.
- Set an optional run condition
Add entry conditions to the path so it only proceeds if the record still qualifies at run time. This stops actions firing against records that changed after the flow first triggered, for example a Case that was already closed.
- Build the action and activate
Drag elements onto the scheduled path to do the work, such as an Update Records or Send Email element. Debug the flow, confirm the Default Workflow User is set in Process Automation Settings, then activate.
The base field the offset is measured from, such as Close Date, Created Date, or a custom date/time field on the record.
How far before or after the Time Source the path runs, expressed in minutes, hours, or days (for example 3 Days After).
Optional criteria re-checked when the time arrives, so the path runs only if the record still matches.
The user, set in Process Automation Settings, that executes scheduled paths and other background automation.
- Scheduled paths work only with the Actions and Related Records (after-save) option, not before-save flows.
- Each scheduled path runs in a separate asynchronous transaction, so it does not share governor limits with the original record save.
- If the Default Workflow User is not configured, scheduled paths can fail to run.
- Very short offsets like one minute are less reliable than one hour or more because of queueing and processing time.