Retry failed runs
A run that failed for a passing reason goes on again from the step it stopped on, without sending anything twice.
On this page
Before you start
- Editors only.
- One run at a time.
- Fix the cause first.
Open Runs and show the failed ones.
RunsFailed
You will see The failed runs.
Open the run and read why it failed.
A failed runthe step that failed
You will see The reason, and Retry when it can help.
Retry it.
Retry from failed stepRetry now
You will see Retry started.
If something is off
- There is no Retry on a failed run
- Some failures never mend.
- The retry failed again
- Fix the cause, then retry.
- This run is no longer failed
- Already retried.
Common questions
Does a retry send the same message twice?
No. The run goes on from the step that failed; the steps that already went are not sent again.
Which version of the flow does a retry use?
The version the run started with, even if you have saved changes since.
Why can't I retry a run whose reply window closed?
Meta only allows messages within 24 hours of the person's last message, and that only gets later. If the window is closed when the retry reaches a message, the run ends as skipped.
For agents: plain text of this guide · all guides
For agents
Guide: Retry failed runs
This page: https://commentwatchdog.com/help/flow-builder/retry-failed-runs
Topic: Flow builder
Time: about 2 minutes
Who can do it: Owner, Administrator or Manager
Author: https://anantgupta.xyz (Anant Gupta, founder of CommentWatchDog)
Start in the app: https://app.commentwatchdog.com/en/inbox
Result when done: A run that failed for a passing reason goes on again from the step it stopped on, without sending anything twice.
Context: Some failures mend themselves: your API was down, Meta's sending limit ran out, the page's connection needed a reconnect that you have since done, or a block was lifted. For those, a failed run offers Retry from failed step. It walks on from the step it stopped on, on the version of the flow it started with; what already went is not sent again. A closed reply window, the step cap and an AI answer that was missing are never offered, because a second try would not change them.
Before you start
1. Only people who can edit the page's automations can retry.
2. A retry happens one run at a time.
3. Fix the cause first (reconnect the page, bring your API back), or the retry fails the same way.
Steps
Step 1 of 3: Open Runs and show the failed ones.
Where: Runs, in the bar at the top of the canvas; then the chip Failed, above the list. The chip is there only while the flow has failed runs.
Link: https://app.commentwatchdog.com/en/inbox (Open the app)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed.en.webp (The chip Failed, above the list of runs.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed-list-phone.en.webp (The chip Failed on a phone, above the list of runs.)
You should see: The failed runs, newest first.
Step 2 of 3: Open the run and read why it failed.
Where: Click the run. Its path stops at the step that failed, marked with a red triangle; click that step and the box In this run, at the top of its panel, says what went wrong, with the platform's own error under it. The usual reasons: your API did not answer, Meta's sending limit was reached, the page's connection needs reconnecting, Meta refused the message, or the 24-hour window had closed.
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed.en.webp (In this run, on the step that failed: The message was refused, and Meta's error.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed-phone.en.webp (The same box on a phone.)
You should see: When a second try can help, Retry from failed step in the bar above the canvas.
Step 3 of 3: Retry it.
Where: Retry from failed step, in the bar above the canvas that names the run. The bar then asks Retry from the step that failed?: press Retry now (Keep as failed leaves the run as it is). On a phone you can open the failed run and read why it failed; Retry from failed step is on a computer.
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed.en.webp (Retry from failed step, in the run's bar.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-retry.en.webp (The bar then asks; press Retry now.)
Screenshot: https://commentwatchdog.com/media/shots/dm-flow-run-failed-phone.en.webp (On a phone: the failed step and its reason. Retry from failed step is on a computer.)
You should see: Retry started. The run goes on for that person from the step that failed.
If something is off
Problem: There is no Retry on a failed run
Fix: That failure will not change on a second try: a closed 24-hour window, too many steps in a row, or a missing AI answer.
Problem: The retry failed again
Fix: The cause is still there. Reconnect the page, check your API, or wait for Meta's limit, then retry.
Problem: This run is no longer failed
Fix: It was retried already, or it has moved on. Reload Runs.
Common questions
Question: Does a retry send the same message twice?
Answer: No. The run goes on from the step that failed; the steps that already went are not sent again.
Question: Which version of the flow does a retry use?
Answer: The version the run started with, even if you have saved changes since.
Question: Why can't I retry a run whose reply window closed?
Answer: Meta only allows messages within 24 hours of the person's last message, and that only gets later. If the window is closed when the retry reaches a message, the run ends as skipped.
Related guides
Follow a run step by step: https://commentwatchdog.com/help/flow-builder/follow-a-run-step-by-step
Send an HTTP request from a flow: https://commentwatchdog.com/help/http-requests/send-an-http-request-from-a-flow
Read the numbers on a flow: https://commentwatchdog.com/help/flow-builder/read-the-numbers-on-a-flow
Plain text of this guide: https://commentwatchdog.com/help/flow-builder/retry-failed-runs.md
All guides for assistants: https://commentwatchdog.com/help/llms.txt

