Official product documentation

How to troubleshoot errors in Zap workflows

Published by Zapier Help Centre.

Published
Publication date unavailable
Accessed
26 September 2026
Read the original source

Evidence

What this source supports

  1. 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.
  2. 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.

Source handling

Link and citation record

Copyright Zapier. Linked and paraphrased only. Run history, retention, and recovery features depend on the current plan.