Dead-letter queue (DLQ) — Dead-Letter Queue
Nedir Dead-letter queue (DLQ)?
Bu terim şu anda yalnızca İngilizce olarak sunulmaktadır.
A dead-letter queue (DLQ) is the retry-exhaust lane failed webhook deliveries land in after the retry pipeline exhausts every attempt — a delivery burns through about ten attempts over roughly four hours of exponential backoff, then moves to the DLQ instead of silently dying. Deliveries in the queue stay inspectable and replayable for a fixed window, so an already-disabled endpoint doesn't permanently lose its events.
More detail
Orbit's DLQ lane holds entries for 7 days and you replay one back into the retry pipeline over the Webhooks API (GET /webhooks/dlq, POST /webhooks/dlq/{id}/replay) or through the dashboard's Developer → Webhooks → Dead-letter queue view. A DLQ entry is still recoverable — distinct from a suppressed recipient (a blocked addressee on the send path) and from a quarantined artifact (an integrity-check failure on recordings or archives).
Triage the lane before replaying: a signature mismatch or a flapping receiver will re-fail, while a disabled endpoint entry needs the endpoint re-enabled first. For recurring patterns — 401/403/404/410 from the receiver, 50+ consecutive failures auto-disabling the endpoint — the DLQ is the diagnostic starting point, not the destination.
Sık sorulan sorular
- How long does a webhook delivery stay in the DLQ?
- Seven days on Orbit. After the retry tier exhausts (~10 attempts over ~4 hours), the delivery moves to the dead-letter queue and stays replayable for a week before the record ages out.
- Why is my webhook in the DLQ instead of retrying?
- Usually the receiver returned a proven-dead response (401/403/404/410) or accumulated 50 consecutive failures, at which point Orbit stops retrying and parks the delivery in the DLQ so the queue doesn't spin forever on a dead endpoint.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.