Replay failed Zap runs

Manually replay failed Zap runs

If you're on a paid plan, you can manually replay any Zap run with steps that halted or errored.

• Go to Zap History.
• Select which Zap runs to replay. You can use the dropdown menus to filter Zap runs by status, date range, owner, folder, app, or Zap name.
  • To individually select Zap runs to replay, select the checkbox next to each Zap run.
  • To bulk select Zap runs to replay, click the checkbox dropdown menu in the upper left and select:
    • Select shown to select all the Zap runs on the page.
    • Select all (5000 at a time) to select up to 5,000 Zap runs.
• In the upper left, click Play [x].
• A notification window will open to indicate that the Zap run is replaying.
  • Here, you can monitor the status of your replay job.
  • Once it's complete, you'll see a summary of the results.

Turn on autoreplay for failed Zap runs

If you're on a Professional plan or higher and enable Autoreplay, Zapier will attempt to retry any steps in a Zap run that fail due to temporary errors or downtime. Autoreplay will retry the step again immediately, and then a few more times if there is still an issue.

• Go to the Zap Runs tab in your Zap History.
• In the upper right, click to toggle the Autoreplay switch on.

Enable autoreplay for an individual Zap

In Zapier for Companies accounts, members can override the account-wide Autoreplay settings by enabling Autoreplay for an individual Zap.

• Open your Zap in the Zap editor.
• In the right sidebar, click Settings.
• In the Autoreplay override section, select an option for this Zap:
  • Use account setting: the Zap will autoreplay according to the current account-wide setting shown in parentheses.
  • Always replay: the Zap will always autoreplay when there’s an error.
  • Never replay: the Zap will never autoreplay when there’s an error.

Note

This feature is only available to Company accounts.

How Autoreplay works

• If a step in a Zap run fails, Zapier will retry the step up to 5 times. While Autoreplay is active:
  • Zapier will not send any error notification emails.
  • Your Zapier Manager Zaps will not trigger.
  • You can still manually replay the failed step.
• Zap runs that are being replayed (or scheduled to be replayed) will show up as "Scheduled" in Zap History.
• Zapier backs off after each successive failed retry attempt on this schedule: 5 minutes, 30 minutes, 1 hour, 3 hours, 6 hours. This means that if the Zap errors at 1:00 PM, Autoreplay will try again at 1:05, 1:35, 2:35, 5:35, and 11:35. The back-off schedule implies the final retry happens approximately 10 hours, 35 minutes after the first error.
• If you edit your Zap after the original error occurs, any future Autoreplay attempts will use the current version of the Zap. This gives you the chance to update your Zap to help with preventable errors.
• When Autoreplay attempts to retry a step, if the Zap is off, or if you've disabled Autoreplay between autoreplay attempts, no additional retry attempts will run.
  • If you turn your Zap off between retries, it won't affect the retry schedule as long as you turn the Zap on before the next retry attempt.
• Only Errored steps can start Autoreplay, but any Halted or Errored steps in the Zap will also replay when the attempt occurs.
• If Zapier cannot successfully replay the Zap run after the last attempt (approximately 10 hours later):
  • Zapier will send you an email notifying you of the error.
    • This is the only notification about the error Zapier will send if you enable Autoreplay.
  • Zapier will trigger any Zapier Manager Zaps you have.

Troubleshoot steps that can't be replayed

Zapier may not be able to replay a step in a Zap run for any of the following reasons:

• The Zap is off. Turn on your Zap to replay these steps.
• The Zap has been deleted. Steps associated with a deleted Zap will not replay.
• The Zap has changed too much. Steps associated with a Zap that has changed significantly will not replay. This includes changes to:
  • The order or number of steps in the Zap.
  • The apps used in the Zap.
• The step is too old. Steps that are older than 2 months will not replay.
• The step has already run successfully. Steps that have already run successfully will not replay.
• Filter and path steps are never replayed. The original info used to evaluate whether filter or path conditions were met will remain the same even if info from previous steps changes after replay.
• The step is already scheduled to replay. You can't manually replay steps that are already scheduled to replay.
• The Zap runs are marked as Held. The Autoreplay feature won't replay Zap runs with a Held status. This status flags potential issues like webhooks breaking or if more info is sent than expected. You must manually replay them instead.