Retry a failed run

When a run fails, you can retry it. A retry starts a new run that picks up at the step that failed and reuses the saved results of the steps that already worked. The failed run stays exactly as it was, and the two runs link to each other.

When to use this

Retry a failed run when you want the same trigger data to go through the workflow again:

• The failure was temporary, such as a rate limit or an outage on the other service, and the service is back.
• You fixed the step that failed and published the fix.
• You reconnected an integration whose connection had stopped working.

Only failed runs can be retried. A completed run, a cancelled run, and a run that is still in progress have no retry. A run that stopped because someone rejected an approval has no retry either: the rejection was a decision, not a failure.

To pause, resume, or cancel a run that is still in progress, see Pause, resume, or cancel a run.

What a retry does

A retry never changes the failed run. It starts a new run with its own run ID, and you can open either one from the other.

A retry always runs on your newest published version, not the version the failed run used. That is what lets you fix a step, publish, and retry. The button and the confirmation name the version, for example version 7, and the confirmation tells you which version the failed run used.

There are two ways a retry can start, and the run's page offers the one that fits:

Publish your fix first

If the run failed because of something in the workflow, fix it and publish before you retry. The retry uses the newest published version, so an unpublished draft has no effect on it.

You can change the step that failed, and any step after it, as much as you need. Those steps run fresh.

Changing a step that comes before the failed step is different. The saved results of the earlier steps no longer fit the new version, so the run cannot pick up where it stopped, and only Run again is offered.

If the failure was an expired or broken connection, reconnect it first. See Reconnect an integration.

Retry one run

1. Open the failed run

   Go to Monitor in the workspace sidebar, then Runs. Set the Status filter to Failed and click the run's ID.

2. Click the retry button

   At the top of the run's page, click Retry from failed step · version N or Run again · version N, where N is your newest published version. The same action is in the Run actions menu as Retry….

3. Read what the retry will do

   A confirmation opens. For Retry from failed step, its title is "Retry from the failed step?". It lists each earlier step with Keeps its result and the step the new run starts at with Runs again.

4. Confirm

   Click Retry from followed by the step's name, or Run from the start. To leave the run alone, click Keep as is. A "Retry started" message appears, and the page opens the new run as soon as it exists.

If a newer version is published while the confirmation is open, it updates and reads "A newer version was just published. Check the details and confirm again." Nothing starts until you confirm again.

When the failure was inside a loop or a parallel step

A retry cannot start in the middle of a loop or a parallel step. It starts at the loop or the parallel step itself, so the whole block runs again.

The confirmation warns you before you confirm. For a loop it reads like "Item 3 failed at Send to CRM, inside the loop For each line item", followed by "The retry starts at the loop, so every item runs again, including the 2 that worked." For a parallel step, every branch runs again.

Steps before the loop or the parallel step still keep their results.

When only Run again is offered

Sometimes a run cannot pick up at its failed step. The button then reads Run again, and the confirmation is titled "This run can't pick up where it stopped" and says why:

Under Changed in version N, each step is marked new step, settings changed, connected differently, or removed.

Click Run from the start to send the run's original trigger data through the newest version from the first step.

Retry several runs at once

You can retry up to 25 failed runs in one go from the workspace runs list.

1. Filter the runs list to failed runs

   Go to Monitor, then Runs, and set the Status filter to Failed. A checkbox appears on each row. This is offered on the workspace runs list, not on a single workflow's runs page.

2. Select the runs

   Tick the runs you want to retry. A run that was already retried, or that a rejected approval stopped, cannot be ticked. If you tick more than 25, the button is turned off and reads "Select up to 25 runs at a time" under it.

3. Click Retry selected

   Click Retry selected (n). A confirmation opens, titled for example "Retry 3 failed runs?". Each run starts again from its failed step on its own workflow's newest published version, and the steps that worked keep their results.

4. Choose what happens to runs whose workflow changed

   Leave If a workflow changed before the failed step, run it from the start instead unticked to leave those runs for you to review. Tick it to run them from the start. It is unticked every time the confirmation opens.

5. Confirm and read the result

   Click Retry n runs. A result appears above the table with one line per run.

Each line of the result names the workflow and the original run, and carries one of these labels:

The result stays until you dismiss it or change the filters.

Verify the retry

• The new run carries a Retry of badge next to its status, with the start of the original run's ID. Click it to open the original.
• The failed run carries a Retried as badge that opens the new run, in the runs list and on its own page. Its retry button changes to Go to retry, and the Run actions menu gains Open retry.
• If your fix worked, the step that failed before now reads completed in the new run.

A run can be retried once. If the retry fails too, open the retry and retry that run.

Troubleshooting

There is no retry button. The run is not a failed run, a rejected approval stopped it, or its original trigger data is no longer available. Check the status badge at the top of the run.

The Retry button is greyed out. A line under the button says what to do:

"Couldn't check whether this run can be retried." The page could not load the retry details. Click Try again. A retry starts a run, so you also need permission to run workflows in the workspace. If the message keeps coming back, check your access to the workspace.

"Too many retries in this workspace. Try again in a minute." A workspace can start up to 60 retries a minute, counting single retries and selected runs together. Wait a minute, then retry the rest.

"This run's original trigger data is no longer available, so it cannot be run again." The data the run started with is gone, so there is nothing to send through the workflow. Start a new run instead.

"This run was already retried" Someone else retried the run first. The page opens that retry.

Related

• Debug a failed run helps you decide whether to retry as it is or fix something first.
• Pause, resume, or cancel a run covers runs that are still in progress.
• The run model explains run statuses and how a run relates to its version.