Automation Answers

Why Did My Zap Stop Working?

A Zap that worked before usually stopped because an app connection expired, a field or permission changed, the Zap was paused, or the source app changed its.

By Automation Ace Editorial TeamReviewed for technical accuracy by Troy TessalonePublished Updated

Short answer

Why Did My Zap Stop Working?

A Zap that worked before usually stopped because an app connection expired, a field or permission changed, the Zap was paused, or the source app changed its payload. Open Zap History at the first failed run, read the earliest error, retest the affected connection, and compare the live fields with the last successful run.

Common causes

  • The connected app token was revoked or expired.
  • A mapped field, folder, view, or status was renamed or removed.
  • Zapier paused the workflow after repeated errors or an owner changed its status.
  • A source-app update changed permissions, payload fields, or trigger behavior.

Diagnostic steps

  1. Find the first failure in Zap History rather than starting with the newest symptom.
  2. Compare that run with the last successful run, especially input fields and account IDs.
  3. Reconnect only the failing app, retest the step, and publish the corrected version.
  4. Send a reversible test record through the complete workflow and verify every side effect.

Example

A CRM administrator removes a custom field used by an action. Older runs succeeded, but new runs fail at that action. Remap the replacement field, publish, and run a new test lead.

Caveats

Replaying failed runs may repeat earlier successful actions. Confirm which steps already completed before replaying.