Process Builder and Workflow Rules have a 1-hour minimum for time-dependent actions — they cannot schedule something for 30 minutes from now. The answer is Record-Triggered Flow with a Scheduled Path set to 30 minutes.
The Flow solution
- Create a Record-Triggered Flow on the object
- Choose Optimize the flow for: Actions and Related Records (after-save)
- Set the trigger condition that should start the wait
- Add a Scheduled Path in the flow’s start element:
- Time Source: “When the record is updated/created” or a field-based offset
- Offset Number: 30
- Offset Unit: Minutes
- Add the action on the scheduled path’s branch
What this looks like in the Flow canvas
[Start: Record-Triggered, after-save]
Run Asynchronously? Yes
Scheduled Paths:
- Name: "After 30 Minutes"
Time source: When the record is created
Offset: 30 minutes after
-> [Update Records / Send Email / etc.]
Alternative: Apex System.schedule()
If you need exactly 30 minutes for a complex orchestration:
public class FollowUpScheduler implements Schedulable {
private Id recordId;
public FollowUpScheduler(Id rid) { recordId = rid; }
public void execute(SchedulableContext sc) {
// do the follow-up work
}
}
// Schedule from a trigger or async context:
DateTime runAt = DateTime.now().addMinutes(30);
String cron = '0 ' + runAt.minute() + ' ' + runAt.hour() + ' ' +
runAt.day() + ' ' + runAt.month() + ' ? ' + runAt.year();
System.schedule('Follow up - ' + recordId, cron, new FollowUpScheduler(recordId));
More code, more flexibility — useful when the work involves things Flow can’t do.
Why Process Builder isn’t an option for 30 minutes
If you set Process Builder to “0 hours” with the intent of triggering immediately, it falls back to immediate execution (same transaction). Setting “1 hour” is the minimum scheduled-action interval. There’s no “30 minutes” option in the UI.
A common use case
SLA escalation reminder — escalate a high-priority case if no agent has responded in 30 minutes.
In Flow:
- Record-Triggered Flow on Case (after-save)
- Entry condition:
Priority = "High" AND Status = "New" - Scheduled Path: 30 minutes after CreatedDate
- On the scheduled branch: check
Statusis still “New” (it might have moved) → if yes, setEscalated = TRUEand email the team lead
What interviewers want
- The crisp answer: Flow Scheduled Path — Process Builder can’t do it
- The unit support: minutes in Flow, hours minimum in Process Builder
- Bonus: the
System.schedule()Apex alternative
Related
- What is the minimum time for time-dependent actions?
Verified against: Salesforce Help — Scheduled Paths. Last reviewed 2026-05-17 for Spring ‘26 release.