rabbitmq-queue verifiedcriticalWritten by the Hub
The queue the engine consumes
in the configuration this is a line
rabbitmq-queue: …Name of the queue MailerQ reads messages from; when it is not set, the engine falls back to the queue named by rabbitmq-outbox.
Values
- Values
any valid queue name- applying
restart required- where it can be set
in the config file · with a startup flag · as an environment variable
In detail
Introduced in 5.15.0 to separate two things that used to share one directive: the name of the queue to read, and the routing key under which messages are published for sending. Older configurations set only rabbitmq-outbox and relied on it meaning both, which is exactly what the stock config still does — it has no rabbitmq-queue line. The fallback was verified on the stand: renaming rabbitmq-outbox moved all ten consumers to the new queue and renamed the whole delay ladder with it. Set this explicitly on any node where the reading queue and the publishing key are not the same thing.
What happens if you get it wrong
Set to a queue nobody publishes to.The node sits idle with ten consumers attached and no work, and nothing reports an error.inference · inference
Changed on a node with messages still in the old queue.Those messages are orphaned: the queue keeps them, no consumer remains, and they are invisible in the console, which only shows the queue the engine reads.verified by experiment · inference