For anyone encountering a similar issue: when using @golevelup/nestjs-rabbitmq in a multi-instance microservices setup, your consumer instance must be configured as an HTTP server. Using RMQ transport in NestJS will not work as expected.

This is because RabbitMQ's Pub/Sub pattern operates over TCP, requiring a different approach for handling multiple instances.