Scheduled Actions are time-based automation actions that execute X minutes / hours / days after a trigger event — "send a follow-up email 3 days after Case creation," "create an escalation task 1 hour before SLA breach." Modern Salesforce uses Flow's Wait elements; legacy systems used Process Builder Scheduled Paths or Workflow Time-Dependent Actions.
- For modern setups: build in Flow Builder
Setup → Flows → New Flow → Record-Triggered Flow → after-save mode. Add a Scheduled Path.
- Set the Scheduled Path's offset and time-source field
Offset: X minutes / hours / days. Time Source: a field on the record (CreatedDate, custom date) that anchors the schedule.
- Add the actions that should fire on schedule
After the Scheduled Path element, add Update Records / Send Email / Create Records elements. They execute when the schedule fires.
- Save and Activate the Flow
Active flows queue scheduled actions when matching records are created/updated. Inactive flows don't queue.
- For legacy: see workflow-time-trigger and process-builder Scheduled Paths
Legacy paths exist but are deprecated for new development.
- Monitor the queue
Setup → Paused and Failed Flow Interviews shows pending scheduled flow runs. Setup → Monitor Workflow Services shows legacy Time-Based Workflow Queue.
Recommended for new automation.
Deprecated.
Deprecated.
- Scheduled actions queue based on the trigger time, not the action time. Editing the underlying record may move or remove queue entries depending on flow / rule re-evaluation logic.
- Failed scheduled actions accumulate. Periodic cleanup of Paused and Failed Flow Interviews / Time-Based Workflow Queue is necessary org hygiene.
- Schedule offset is calculated in Salesforce server time (UTC by default unless you specify timezone-aware date formula). Misalignments produce off-by-hours surprises across timezones.