---
title: "Viktor (@viba88) | Hashnode"
description: "Viktor (@viba88) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@viba88"
---

@viba88

# Viktor

@viba88 · Joined October 2026

### [Did the replay work? Finding the RabbitMQ dead letters that come back](https://warrenops.hashnode.dev/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back?utm_source=hashnode&utm_medium=feed)

A 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.dev](https://warrenops.hashnode.dev/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back?utm_source=hashnode&utm_medium=feed)

[Oct 22](https://hashnode.com/posts/did-the-replay-work-finding-the-rabbitmq-dead-letters-that-come-back/6ad9ba789a7428885692e839)

### [Replay only some RabbitMQ dead letters: by exception, header or routing key](https://warrenops.hashnode.dev/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key?utm_source=hashnode&utm_medium=feed)

Put 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.dev](https://warrenops.hashnode.dev/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key?utm_source=hashnode&utm_medium=feed)

[Oct 20](https://hashnode.com/posts/replay-only-some-rabbitmq-dead-letters-by-exception-header-or-routing-key/6ad70720ca2952d3c83ec7c9)

### [Your quorum dead-letter queue can drop the dead letters: x-delivery-count travels along](https://warrenops.hashnode.dev/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along?utm_source=hashnode&utm_medium=feed)

On 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.dev](https://warrenops.hashnode.dev/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along?utm_source=hashnode&utm_medium=feed)

[Oct 19](https://hashnode.com/posts/your-quorum-dead-letter-queue-can-drop-the-dead-letters-x-delivery-count-travels-along/6ad5b2379f8da2db48e99141)

### [MassTransit on RabbitMQ: what ends up in \_error and \_skipped, and how to move it back](https://warrenops.hashnode.dev/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back?utm_source=hashnode&utm_medium=feed)

What 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.dev](https://warrenops.hashnode.dev/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back?utm_source=hashnode&utm_medium=feed)

[Oct 15](https://hashnode.com/posts/masstransit-on-rabbitmq-what-ends-up-in-error-and-skipped-and-how-to-move-it-back/6ad074898cb2984fa69e71da)

### [Replay one message first: a canary for RabbitMQ dead letters](https://warrenops.hashnode.dev/replay-one-message-first-a-canary-for-rabbitmq-dead-letters?utm_source=hashnode&utm_medium=feed)

Before 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.dev](https://warrenops.hashnode.dev/replay-one-message-first-a-canary-for-rabbitmq-dead-letters?utm_source=hashnode&utm_medium=feed)

[Oct 14](https://hashnode.com/posts/replay-one-message-first-a-canary-for-rabbitmq-dead-letters/6acf20b15277e55e568d3f57)
