Scheduled paths in record-triggered flows allow you to delay part of the flow’s execution to a specific time after the triggering event. You can configure the schedule based on when the record was created or updated, or even use a date/time field on the record. This is especially useful for time-based actions like reminders, follow-ups, or conditional updates. Unlike the immediate path, scheduled paths have built-in retry logic. If the actions in a scheduled path fail, Salesforce automatically retries them. This makes scheduled paths more resilient and reliable for handling delayed or time based actions.
Here’s how the retry logic in record-triggered flow scheduled paths works.
How the Built-in Retry Logic Works
Just like the immediate path, if a scheduled path interview fails, an error email is sent and the failure appears in the Failed Flow Interviews section in Setup. However, scheduled paths include built-in retry logic. The system automatically retries the path up to four more times. 15 minutes after the initial failure, then 30 minutes later, followed by retries 60 and 120 minutes apart, totaling four retries over nearly four hours.
Here is the breakdown of the retry mechanism:
- 15 minutes after the initial failure.
- 30 minutes after the first retry.
- 1 hour (60 minutes) after the second retry.
- 2 hours (120 minutes) after the third retry.
When a retry is scheduled, you can track it in the Time-Based Workflow page. If some flow interviews in the same transaction succeed while others fail, the entire transaction is rolled back, and the successful interviews are retried immediately. In this case, the maximum number of retries is two.
Example
Let’s say you have a record-triggered flow with a scheduled path that updates the Case status. Now, assume that a validation rule is blocking this change, causing the flow to fail.
Since the failure occurred in a scheduled path, the system will retry up to four more times. Therefore, if the error persists, you will receive a total of five error emails. One for the initial failure and four from the built-in retry logic.
Moreover, you can view all of these failures in the Failed Flow Interviews section in Setup.
Importance of the Retry Logic
The retry mechanism in scheduled paths is important because it gives your automation a second chance to succeed.
First, it gives you time to fix issues (like a validation rule or missing data) before the next retry attempt. This means you don’t need to manually rerun the process. You have up to 3 hours and 45 minutes across the retry window to resolve the problem.
Second, if the failure is due to a temporary issue like record locking, the scheduled path may succeed in one of the subsequent retries. This improves the reliability and resilience of your flow.
The post Retry Logic in Record-Triggered Flow Scheduled Paths appeared first on Salesforce Time.