Message expiration not working automatically

[felzend]

I'm running on Docker w/ image "rabbitmq:3.8.14-management"

Publishing a message with expiration to Q1 (which has these headers declared).

x-dead-letter-exchange:	my_exchange
x-dead-letter-routing-key: Q2_routing_key

When the message on Q1 expires, it won't go to Q2 automatically, I have to go on the Get Message(s) button on Q1 and click it, so the trigger happens.

I have used RabbitMQ for a time with similar approaches and this has never happened to me.

Any idea?

[michaelklishin]

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(

[michaelklishin]

See TTL Caveats. If head-of-the-line messages are not consumed, expired messages won't be expired. They are expired at (attempted) delivery time.