Test flows and recover from problems

Use execution history and versions to understand a workflow.

When to use this. An automation stopped midway or produced an unexpected result.

What you’ll need. The run time, sample record, and permission to inspect execution history.

Run a small test
Use sample data and a limited action scope. Avoid testing with live customer messages or payments unless that is intentional.
Find the failing step
Review execution history and the state recorded for the run. Check input values, account connections, and the expected response from external services.
Resume or adjust
Use available debug-resume controls to inspect a paused state. Before repeating an action, check whether the original run already performed it.
Restore a known version
Review saved versions and roll back when necessary. Test the restored version before returning the flow to normal use.

How to know it worked

You can locate the failing step and verify a corrected run without duplicating completed actions.