When using Symfony messenger to consume messages, the default behaviour is to poll each receiver in order. If a receiver has returned messages that were handled, the loop starts to poll the first receiver again. With a comment at the logic stating:

after handling a single receiver, quit and start the loop again
this should prevent multiple lower priority receivers from
blocking too long before the higher priority are checked

Which makes sense, if you have high and low priority receivers. But I've often found the need for equal polling of receivers, when they don't have different priorities. In that case it is not desired to keep receiving from the first receiver as long as it is returning messages. But to poll each receiver in order.

A random order could also be beneficial for load-balancing. E.g. If you have 2 consumers polling the same receivers in order, and they'd start at the same time, the receivers that are last to be polled will have a handling delay. Until the consumers happen to diverge. But if the order of receivers is randomized, each receiver would likely have less delays between polling.

A --strategy=priority|ordered|random command option (and worker option) could expose this as a feature. I'm curious about the thoughts on this.

I have not yet added a changelog line (or tests) as I'd first like to get input on this idea as a concept.