Zapier Error 400, 401, 403, 422, 429 and 500 Explained
Quick answer
Open the failed step in Zap history and read the HTTP log: 401 means reconnect, 403 permissions, 422 bad data format, 429 rate limit, 500 usually temporary so replay. Fix the cause then replay the run.
Most likely fix: Read the error
How to fix it
Try these in order — the most common fix is first.
1. Read the error
- Zap history > errored run > failed step > Troubleshoot tab and HTTP log
Did this fix it?2. Apply the fix
- 400/422: check required fields, use Formatter
- 401: reconnect the app
- 403: check access in the app
- 429: slow the Zap with Delay or reduce volume
- 500: replay, check status pages
Did this fix it?3. Recover data
- Replay failed runs; Autoreplay retries temporary failures
- Add custom error handling for important steps
Did this fix it?
Symptoms
A Zap run shows Errored with a status code or vague app error.
Why it happens
- 400: invalid or missing input
- 401: credentials expired
- 403: no permission
- 404: record not found
- 422: wrong data format
- 429: rate limit exceeded
- 500 or timeout: app or Zapier side issue
This guide also covers
- zapier error 422
- zapier 429 too many requests
- zapier error 500
- zapier errored run
Still not working?
If Zapier keeps failing, you're not alone. See every Zapier problem users report or the alternatives people switch to.
Done fighting Zapier? Our small team builds your own Zapier alternative, made for how you work. On your domain or hosted by us. Price agreed together.
Get a quote