Walk a Broken-Zap Incident
Respond to a broken no-code automation by containing impact before replaying or editing.
Incident Hundreds of failed runs appear, but some earlier steps may already have written production records. Replay can be more damaging than the original failure if partial success is ignored. Incident order Pause -> scope -> repair -> selective replay Treat broken automations like operational incidents, not ordinary edits. Shortcut Fix the step and replay everything Recovered records without duplicate damage. A failed run can still have successful side effects. 01 Contain 02 Scope 03 Recover Step 1 New invoice events are still entering the workflow every few minutes.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in