Replay Failed Executions in One Step
When a run fails, fix the cause and replay it, instead of rebuilding the workflow or asking the user to start again.
Recover, don’t rebuild
Every run is kept, so a failure is something you can fix and finish.
Replay failed runs
Run a failed execution again once the cause is fixed.
Same input
Replays use the original input, so nothing has to be re-entered.
No workflow rebuild
Recover without rebuilding or re-triggering the whole workflow.
Find the failure first
Logs show exactly which step failed and why before you replay.
Works with retries
Automatic retries handle temporary errors; replay covers the rest.
Per customer
Replay a single customer's run without touching anyone else's.
How it works
Spot the failure
See the failed run and the step that caused it in the logs.
Fix the cause
Reconnect an account, update a setting, or fix the data.
Replay it
Run it again and confirm it succeeds.
When teams use replay
Expired connections
Replay runs that failed while a user’s connection needed reauthorizing.
App outages
Finish the work that failed while a connected app was down.
Bad data
Correct a bad value and replay the run instead of starting from scratch.
FAQs about Execution Replay
What is execution replay?
It lets you replay failed executions when appropriate, helping you recover from errors without rebuilding the entire workflow.
How is replay different from retries?
Retries run automatically for eligible temporary errors. Replay is for runs you choose to run again, usually after fixing the cause.
Does a replay use the original data?
Yes. A replay runs with the original input of the failed execution.
Can I see why a run failed before replaying it?
Yes. Execution logs show the failing step and the error.
Turn failures into finished work
- Managed auth
- Per-customer connections
- Actions & triggers
- Data mapping
- Monitoring & logs
- Your branding