Zapier Catch Hook 404 when the Zap is off: Sume webhook retries

If a Sume job finishes while the receiving Zap is off, Zapier's Catch Hook answers 404, and Sume counts that as a failed attempt. It retries up to 10 times with a fixed delay (30 seconds by default). Turn the Zap back on within that window, or call redeliver afterwards, and the terminal event arrives.

The 404 behavior is from Zapier's help article, updated May 29, 2026, for static Catch Hook and Catch Raw Hook URLs. Sume's rules are from its webhooks docs. Both read 2026-10-01.

What changed on the Zapier side?

Previously these triggers returned 200 whether or not a Zap was behind the URL. Now, per the article, "If your Zap is off or deleted, Zapier will return a 404 response for incoming webhooks". It also notes a short delay after turning a Zap off when 200 may still come back, and that reactivating returns it to 200.

How does Sume treat that 404?

Sume's docs say network errors and non-2xx responses are retried until attempts are exhausted. A 404 is non-2xx, so it is a failed attempt, not a lost job: the job still reaches its real terminal state.

How do I recover after the retries run out?

Redeliver re-POSTs the real terminal event with a fresh timestamp and signature, and the docs say it still works after automatic attempts are exhausted without consuming one of the automatic 10. The target URL stays the same, so the Zap must be on first. Dedupe on job_id in case an earlier attempt did land. More in debugging failed deliveries.