Skip to content
MapleGatherMapleGather Help

Webhook deliveries failing or dead

Your webhook endpoint is showing a “failing” health badge or a “Delivery stopped — exceeded retries” (dead) state, or you are seeing failed or dead rows in the delivery log.

What’s happening

Section titled “What’s happening”

Failing health badge (on an active endpoint): MapleGather detected that recent deliveries to your endpoint are returning non-2xx HTTP responses. The endpoint is still active and MapleGather is still retrying. The badge is an early warning — not a status change in the endpoint record itself.

Dead endpoint: The retry budget was exhausted. MapleGather attempts delivery up to six times over approximately 24 hours using exponential backoff. After all six attempts fail, the endpoint transitions to dead and delivery stops. You must re-enable the endpoint after fixing your receiver.

How to fix it

Section titled “How to fix it”
  1. Go to Admin & Security > Integrations > Webhooks.
  2. Find the failing or dead endpoint and select ⋮ > View deliveries.
  3. In the delivery log, expand a failed or dead row. The detail opens with the cause: the last HTTP response code (for example, 500), the attempt count, and when the next retry will fire (or “retries exhausted — dead-letter” for a dead row).
  4. Use the response code to diagnose the issue on your receiver:
    • 500 — an error in your receiver. Check your server logs for exceptions.
    • 404 — your receiver URL may have changed. Update the endpoint URL using Edit endpoint (webhook_endpoints_update), or create a new endpoint at the correct URL.
    • 401/403 — your receiver is rejecting the request, possibly due to an HMAC signature mismatch. See HMAC signature verification failing.
    • 408/504 — your receiver is timing out. The server-side default timeout is 10 seconds. Reduce your receiver’s processing time or acknowledge the request immediately and handle the work asynchronously.
  5. Fix the issue on your receiver.
  6. If the endpoint is now dead, select Re-enable on the endpoint detail page. Read the confirmation (“Re-enabling resumes delivery from active. Past failed deliveries are not auto-resent — use Replay for those.”) and confirm.
  7. To recover missed deliveries, replay them individually from the delivery log. Select Replay on each delivery row. Deliveries older than 30 days cannot be replayed.

If the endpoint is still active with the failing badge: once your receiver starts returning 2xx, the badge clears automatically — no re-enable needed.

If that didn’t work

Section titled “If that didn’t work”

If the endpoint goes dead again after re-enabling, the underlying issue on your receiver was not fully resolved. Check the new failure rows in the delivery log for the response code and try again.

For persistent HMAC verification failures, see HMAC signature verification failing.

Contact support if you cannot identify the root cause from the delivery-log response codes.

Section titled “Related”