---
schema_version: "1"
id: 8257ac80ac822eaf3fa64f0164cc355567346cbbef5c847cffb10a93118b2079
title: Troubleshooting Flow Retries
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_troubleshoot_retries.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_troubleshoot_retries.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: fcd898c50273cc786c523fa1249dc525c9bebaf85cb98c5abd5b9ce830094582
description: 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.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# 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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d354093e41">Flow Types</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d354093e44">Time Based Retry</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Flow Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e41 ">
              <ul>
                <li>Record-Triggered After Save Flow After Save that runs a path immediately</li>

                <li>Record-Triggered Before Save Flow that runs a path immediately</li>

              </ul>
            </td>

            <td data-label="Time Based Retry" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e44 ">No</td>

          </tr>
          <tr class="">
            <td data-label="Flow Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e41 ">
              <ul>
                <li>Platform Event—Triggered Flow</li>

                <li>Data Cloud-Triggered Flow</li>

              </ul>
            </td>

            <td data-label="Time Based Retry" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e44 ">No</td>

          </tr>
          <tr class="">
            <td data-label="Flow Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e41 ">
              <ul>
                <li>Record-Triggered Flow after transaction is committed</li>

                <li>Record-Triggered Flow that runs a scheduled path</li>

                <li>Schedule-Triggered Flow</li>

                <li>Flow types with a wait element that resumes from a time-based event</li>

              </ul>
            </td>

            <td data-label="Time Based Retry" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e44 ">Yes, fixed schedule: 15, 30, 60, and 120 minutes. After the final attempt, the flow
              interview fails.</td>

          </tr>
          <tr class="">
            <td data-label="Flow Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e41 ">
              <ul>
                <li>Segment-Triggered Flow</li>

                <li>Automation Event-Triggered Flow</li>

              </ul>
            </td>

            <td data-label="Time Based Retry" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e44 ">Yes, schedule depends on error type. If these flow types contain unrecoverable
              errors, such as invalid inputs, they don’t perform a retry.</td>

          </tr>
          <tr class="">
            <td data-label="Flow Types" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e41 ">Screen</td>

            <td data-label="Time Based Retry" class="slds-cell-wrap" style="vertical-align:top;" headers="d354093e44 ">No</td>

          </tr>
        </tbody>
      </table>

## 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](https://help.salesforce.com/s/articleView?id=platform.flow_build_logic_fault.htm&type=5&language=en_US).