Loading
Prepare for Email to Become the Default Login ExperienceRead More
Intermittent freezing when using using certain browser versionsRead More
Automate Your Business Processes with Salesforce Flow
Troubleshooting Flow Retries

Troubleshooting Flow Retries

Learn how a flow is run again after it failed to finish successfully. A flow retry is when a flow runs again to process records that failed to save successfully.

Time Based Retry

If a flow interview encounters an unhandled error, the transaction is rolled back and some flows schedule a time-based retry. A time-based retry restarts flow interviews from start or resume on a schedule with intervals typically lasting at least one minute, and often longer.

Flow Types Time Based Retry
  • Record-Triggered After Save Flow After Save that runs a path immediately
  • Record-Triggered Before Save Flow that runs a path immediately
No
  • Platform Event—Triggered Flow
  • Data Cloud-Triggered Flow
No
  • Record-Triggered Flow after transaction is committed
  • Record-Triggered Flow that runs a scheduled path
  • Schedule-Triggered Flow
  • Flow types with a wait element that resumes from a time-based event
Yes, fixed schedule: 15, 30, 60, and 120 minutes. After the final attempt, the flow interview fails.
  • Segment-Triggered Flow
  • Automation Event-Triggered Flow
Yes, schedule depends on error type. If these flow types contain unrecoverable errors, such as invalid inputs, they don’t perform a retry.
Screen No

Callout Actions

This flow follows the general process for making a callout: The callout must occur before Salesforce records are updated, because Salesforce doesn’t allow updates to its records before accessing data outside Salesforce. Consider this flow after it’s saved.

  • A callout that updates data outside Salesforce: Update External Opportunity that uses an External Services action
  • Updates Salesforce data: Update an Opportunity based on the results from the External Services action

If, in a batch of two flow interviews, one fails its callout while the other completes and updates Salesforce records, no rollback or retry occurs because the failing interview made no Salesforce updates.

If, in a batch of two flow interviews, both succeed in their callouts but one fails its updates to Salesforce while the other succeeds, the successful flow rolls back and retries, with a maximum of 2 retries.

Actions that perform callouts can’t be rolled back.

Not every flow element that appears to require a callout does.

Flow Element Is it a Callout?
Send Email Action No
Post to Chatter Action No
Send Slack Message Action Yes
Create, Update, and Delete Records for Salesforce objects No
Create, Update, and Delete Records for External Objects Yes
External Services Actions Yes

Fault Paths

A fault path connected to an element handles all errors occurring on that element, and it's the only way to guarantee that a flow interview doesn't fail and that retries aren't attempted. See Customize What Happens When a Flow Fails.

 
Loading
Salesforce Help | Article