Webhook Retry Policy
Gluey's webhooks await a response for 30 seconds after dispatching a message. If there's no response within this timeframe, the message is set to be retried. The retry mechanism follows an exponential backoff strategy, attempting delivery again at the following intervals:
- 10 seconds
- 30 seconds
- 1 minute
- 5 minutes
- 10 minutes
- 30 minutes
- 1 hour
- 3 hours
- 6 hours
- Every 12 hours up to 24 hours
If a response is received within 3 minutes, Gluey's webhooks will try to remove the event from the retry queue, although duplicates might still occur since we operate on an at least once basis.
There is a slight jitter (randomisation) added to each retry interval, and some retries may be skipped if the endpoint remains unhealthy, is down for an extended period, or seems overloaded.
90-Day Dead-Letter Queue (DLQ)
After 24 hours, undelivered events are moved to a dead-letter queue, where they remain for 90 days before being deleted.
Gluey can manually reattempt to send all events within this period upon request. For such requests, contact engineering@gluey.ai.
Delayed Delivery
If an endpoint repeatedly fails to deliver, Gluey will start delaying the delivery and retries of events to that endpoint. For instance, if the first 10 events to an endpoint fail, Gluey will delay further retries and new deliveries to prevent overwhelming the system, sometimes for several hours.
This delay helps to prevent Gluey's retry policy and delivery volume from overloading systems with persistent issues.