Follow the run log, and retry or resume from the failed step
Every automation has a list of runs and a plain-language timeline for each run. You can retry a failed run from the start or resume it from the step that failed.
Permission to view workflows; retrying needs permission to edit
You need: Permission to view workflows; retrying needs permission to edit
Steps
1
Open the automation and press History.
2
Filter the runs under Show runs, or search with Find a record by name.
3
Open a run to see its timeline.
4
Fix the cause, then press Start over or Continue from step ….
Run statuses
Status
Means
Running
Working right now
Waiting
At a delay, an approval, a wait for a reply, or an action being retried
Done
Finished successfully, including “Completed — reached the goal”
Needs you
Stopped with an error, or with an unconfirmed send
Skipped
The trigger or the conditions turned it down, “This record already ran”, or the automation was paused
The timeline
Each line shows the time, a mark, and a sentence that says what happened.
Mark
Means
A check
The step went through, such as “Sent the message to the chat.”
A cross
The run stopped here; the sentence says why, and what to fix
A dash
The step was passed by, such as “Skipped — this step is turned off.”
A temporary failure reads “Try 2 of 5 failed — … Trying again shortly.” A send that may or may not have arrived says it’s “not sure it went out”.
Retry or resume?
Start over
Continue from step …
Starts from
The beginning, as a new run
The step that failed
Completed steps
Run again
Not run again
Condition
A failed run
A failed run, the automation is on, and the step is still the same type
Version
The current version
Moves to the current version, so it picks up your fix
An “unconfirmed” step asks “Send it again?”, because the message may have arrived. Open the chat first, then press Send again and carry on.
If you changed the failed step’s type or deleted it, retry from the beginning.
Counts on screen
History shows how many records went through the automation in the last 30 days. In the Story view, At a glance covers the last 7 days: how many went through, finished smoothly, and need you.
The workflows list shows Last ran and This week for each automation, and Needs you lists the automations whose last run stopped and the approvals waiting for you.
Who sees what?
You only see runs for records you’re allowed to see. The owner sees them all. If your permission is limited, the total shows as a minimum.
If something goes wrong
What you see
Why
What to do
“The run can’t be resumed”
It isn’t failed, or its position isn’t known.
Retry from the beginning.
“The automation’s steps changed”
The failed step was deleted or its type changed.
Retry from the beginning.
“Send it again?”
The message may have arrived.
Check the chat, then confirm sending again.
“Reserved by another run”
Run each record only once is on, and another run already ran.
No need to resume.
I can’t see a run
The record is outside your permission, or the run is older than 30 days.
Ask the owner.
A real example
Shield Security Co.
The situation
15 renewal messages failed because the WhatsApp line disconnected.
What they did
They filtered the runs by Needs you.
They reconnected the line.
They resumed every run from the sending step, so the task-creation step didn’t repeat.
The result
The messages arrived without duplicate tasks.
A made-up company, to show the idea. The numbers are rounded.
Good to know
History shows the last 30 days.
Search takes 2 to 100 characters, and matches the record’s name at the time the run started.
Pressing retry twice within a minute starts only one run.
