Protocols
Saved & recent

Dead-letter queue

Also called: DLQ, dead lettering, dead-letter exchange

A dead-letter queue holds messages redirected out of their normal processing path because they cannot continue under configured rules. Reasons can include rejection, expiry, or a delivery limit. The precise triggers and delivery guarantees depend on the messaging system and its configuration.

For example, a worker repeatedly encounters an unsupported payload version and routes the message for investigation. In RabbitMQ, a dead-letter exchange routes such messages onward to a bound queue; the exchange and queue are distinct. Keeping failed messages helps diagnosis, but correction, replay policy, and duplicate-effect protection still need explicit handling.

Read first
Message broker
Related
Consumer acknowledgment, Delivery semantics, Retry backoff and jitter
Further reading
RabbitMQ — Dead Letter Exchanges
normal queue worker unsupported version dead-letter exchange investigation queue routes message stores message manual corrected replay RabbitMQ routing example
RabbitMQ example: a worker rejects an unsupported payload without requeueing; the normal queue dead-letters it through an exchange to an investigation queue. The dashed path represents an explicit corrected replay, not automatic recovery or a guarantee of lossless transfer.

View in the full Protocols collection