Why a Blueticks Webhook Stops Delivering: Retries, Cooldown and Auto-Disable

If your Blueticks webhook stopped receiving events, your endpoint is probably returning errors or timing out. Blueticks first retries, then pauses the endpoint on a cooldown, and only disables it after sustained failure. These are the values in the current backend settings.

How a failed delivery is retried

• Timeout: each attempt waits 10 seconds for your answer.
• Attempts: up to 8 per event.
• Delays between attempts: 1 minute, 5 minutes, 15 minutes, 1 hour, 2 hours, 6 hours, then 12 hours.

A server error or a timeout is retried. A client error (a 4xx status) is treated as permanent and is not retried, except 408, 425 and 429, which are retried. If you send Retry-After on a 429, Blueticks waits at least that long, capped at 6 hours.

What the cooldown does

When an endpoint keeps failing, Blueticks stops sending every new event at it. After consecutive failed attempts it pauses the endpoint for 1 minute, then 5 minutes, 30 minutes, 2 hours and 6 hours. 6 hours is the longest pause. Each pause is shortened by a random amount of up to 20%.

A 410 Gone jumps straight to the 6-hour pause, without disabling the webhook. An event still waiting after 3 days of pauses is dropped.

When a webhook is disabled

A webhook is disabled automatically only when both are true:

1. It has failed continuously, with no successful delivery, for 3 days.
2. It has had at least 10 failed attempts.

When that happens the owner gets an email. A successful delivery clears the failure state.

Fix checklist

1. Return a 2xx fast. Answer within 10 seconds and do the work afterward. A slow handler counts as a failure.
2. Do not return 4xx for errors you want retried. Use a 5xx, or 429 with Retry-After.
3. Check the server is up. Server errors and timeouts count as failures.
4. Make the handler safe to run twice. An event can arrive again if your answer was slow.

For signatures and the events you can subscribe to, read WhatsApp API delivery status webhooks.

FAQ

Is a webhook disabled after 8 failures?

No. 8 is the number of attempts for one event. Disabling needs 3 days of continuous failure and at least 10 failed attempts.

My endpoint was down for an hour. Did I lose events?

Events are retried for up to 8 attempts, with delays that stretch to 12 hours, so an outage of an hour is covered. An event still deferred after 3 days is dropped.

Building on WhatsApp with webhooks? Start free with Blueticks.