Official product documentation
How to troubleshoot errors in Zap workflows
Published by Zapier Help Centre.
Read the original sourceEvidence
What this source supports
Zapier documents errored, halted, held, handled, and scheduled run states plus history and troubleshooting details.
- Locator
- Sections covering run statuses, history, logs, and troubleshooting; lines 16–32 and 76–106
- Editorial note
- Histories have retention and plan limits. Retries can duplicate side effects.
Zapier documents that an HTTP log can show parameters, headers, and a request body for an errored step.
- Locator
- Section “Review issues in the Zap’s HTTP log”, lines 76–103
- Editorial note
- These fields can contain credentials, tokens, personal data, or confidential content. Keep the source log restricted and share only a redacted link and the minimum context needed for review.
Related advice
Where this source is used
Source handling
Link and citation record
Copyright Zapier. Linked and paraphrased only. Run history, retention, and recovery features depend on the current plan.