> ## Documentation Index
> Fetch the complete documentation index at: https://help.flowforth.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrying & Resuming Runs

> Re-run a failed or canceled automation from where someone left off — or from a step you pick.

Sometimes a run doesn't finish the way you wanted: an email failed partway through, or you canceled a run you actually meant to keep. **Retry** lets you re-run an automation for those people — without rebuilding anything.

Retries always run against the automation **as it exists now**. Because they resolve against your live steps rather than a saved snapshot, even runs from before step history existed can be retried, and any steps you've since deleted simply aren't offered as starting points.

***

## Which Runs Can Be Retried

Retry is available for runs that **failed** or were **canceled** — the ones that stopped without finishing. A run that's still **In Progress** shows **Cancel Run** instead, and a run that already **Completed** doesn't offer Retry, since it finished as intended.

You'll find Retry on an automation's [**People** tab](/automations/managing/monitoring):

* **One person** — click **Retry** on their row.
* **Several at once** — select runs with the checkboxes, then click **Retry** in the action bar.

***

## Choosing Where to Pick Up

When you retry, a dialog asks how each run should resume. There are two modes.

### Resume where each left off

Every selected run continues from its **own next step** — the one right after the step it last completed. Nothing that already happened runs again, so no emails are re-sent.

If a run has no next step to resume from — for example, its last completed step was deleted, or it already reached the end of the flow — it's skipped. When none of your selected runs can resume this way, the option is unavailable and you'll pick a step instead.

### Start everyone from a specific step

Pick a single step, and **every** selected person runs the flow from there. The step picker mirrors your builder: top-level steps, plus each [**If / Else**](/automations/builder/if-else) condition's **Yes** and **No** paths.

* **Starting at a condition** re-evaluates it, routing each person down the Yes or No path based on their list membership at that moment.
* **Starting inside a branch** forces everyone onto that path, skipping the condition check above it. Flowforth warns you when the step you picked is inside a branch.

Before you confirm, a preview tells you how many emails will send from that point. Keep in mind that **any email a person already received will be sent again** if it falls after the step you start from.

***

## No Double Sends

A retry is a brand-new run that begins at the step you choose, so steps **before** that point are never re-executed. Retrying never silently re-sends earlier emails or double-counts your usage — the only re-sends are the ones you opt into by starting from a step someone had already passed. Per-step send limits work exactly as they do on a normal run.

<Note>
  Retrying is always something you start yourself — Flowforth never automatically retries a failed run. If a person still has an **in-progress** run for the automation, a retry won't re-enroll them until that run finishes.
</Note>

***

Want to see exactly where each person got before you retry? Open their [step timeline](/automations/managing/monitoring#step-timeline) from the People tab.