#1MinuteTip In Salesforce Flows, Scheduled Path in Record-Triggered Flow and Schedule-Triggered Flow – they both allow you to schedule actions that should be executed at a point in time in future.
However, one of main differences between the two is that with scheduled path, you have more granular control on when the action will be triggered. Like you can set the scheduled path to execute <x> minutes/hours/days/months “before” or “after” a specific time source.
With scheduled triggered flow, you can schedule to run it only on a daily/weekly basis at a fixed time. So, this is more restrictive and less flexible in this regard.
Scheduling Options Available with Scheduled Path in Record-Triggered Flow
Scheduling Options Available in Schedule-Triggered Flow
Introducing Mastering Salesforce Flows Training Course
Liked this post? We are now offering a complete self-paced, video-based training course on Mastering Salesforce Flows. The course comes with downloadable step-by-step PDF guides, unlimited access, free upgrades, community discussion area, free preview and more. For more details, please click here.
Need Help with Flows?
Need advice on Flows? I also offer advisory & consulting services on Salesforce Flows. So, whether you want to create new Flows or migrate existing automations (Workflow Rules, Process Builder, Triggers) to Flows, I can help you analyze, design, plan & review. To initiate a discussion, please submit the contact form here stating your requirement or schedule a discussion at this URL.
I guess depending on the business the Schedule-Triggered Flow could be more efficient compared with the Scheduled Path in Record-Triggered Flow, because the second one may create a lot of Interview records in SF (as many as the number of records scheduled to be triggered in the future, so it may consume more resources) compared with the first one, it can run let’s say daily and query only the records that meets the criteria and perform the actions all at once.
Another aspect to consider with the Scheduled Path in Record-Triggered Flow is that the Interview is created with a user that triggered the flow. If the user is deactivated before the interview is performed, the flow won’t run.