Zap history

Zap history is the log of everything your Zaps have done. Each run shows the data from the trigger, what every step did and a status, like successful, errored, halted or held.

It's the first place to look when something goes wrong. Open an errored run and the Logs tab shows the app's error message, which usually tells you what broke.

Zapier switches a Zap off by itself if 95% of its runs error and it has run more than 20 times in the past 7 days. Team and Enterprise accounts get an email and a grace period first: 24 hours on Team and 72 hours on Enterprise.

Once you've fixed the problem, you can replay failed or held runs, so you don't lose the data. Autoreplay on paid plans can retry temporary errors automatically, up to five times.

Every client I hand over to gets a short lesson in Zap history, because it's how they'll fix most problems without me. Find the red run, read the error, fix the cause, replay.

I also set up an error alert, so someone hears about a failure the same day instead of finding out a week later when a customer chases. Most errors are boring, like an expired connection or a missing field, and they're quick to fix if you catch them early.

1. Spot An errored run shows up in Zap history Errored
2. Read The Logs tab says a required field was empty Cause
3. Fix Add a Filter so the Zap skips records without it Fix
4. Replay Replay the failed run once the data's fixed Recovered