Did the replay work? Finding the RabbitMQ dead letters that come backA confirmed replay is not a replay that worked. Tag replayed messages, find the ones that die again, and read the result.6 min read·warrenops.hashnode.devOct 22
Replay only some RabbitMQ dead letters: by exception, header or routing keyPut back only the matching dead letters with basic.get, without the nack loop and without losing quorum messages on connection close.8 min read·warrenops.hashnode.devOct 20
Your quorum dead-letter queue can drop the dead letters: x-delivery-count travels alongOn RabbitMQ 4 a quorum DLQ with a delivery limit can drop messages when they are peeked and put back. Why it happens, and the fix.7 min read·warrenops.hashnode.devOct 19
MassTransit on RabbitMQ: what ends up in _error and _skipped, and how to move it backWhat MassTransit puts in _error and _skipped queues, what the MT-Fault headers say, and how to move messages back without a second delivery.6 min read·warrenops.hashnode.devOct 15
Replay one message first: a canary for RabbitMQ dead lettersBefore replaying a whole dead-letter queue, send one message and watch whether it dies again: how long to wait and what a pass proves.7 min read·warrenops.hashnode.devOct 14