Emiel Bom

@cuebit @kiaking Is there any interest in this issue and probable solution?

I think u are using horizon as a queue manager and manage worker processes through horizon. When you mix your artisan commands and horizon you're in a trail and error...

In short .... No, RabbitMQ handles messages, within a queue, with the concept of FIFO (First in, First out). Every message has the same priority. there should be no difference,...

If this answers your question, please close the issue.

Explain queue in job? What should the result be? I think, there is no solution from Laravel's point of view other than what i described above.

Because `alternate-echange` is an option you can define into rabbitMQ. I can see why you want to be able to add this as an option to the declareExchangeCommand. Only i...

@xXcoronaXx If you did solve this issue, can you please please provide some more infomation. Is this still an issue with the latest version?

In my opinion you don't reconnect. Workers work... And when a error occurs, your worker should probably die. A manager like horizon or cron jobs an schedulers or a supervisor...

Publishers: are responsible for creating queues. Consumers just consume when queues exist with messages. > Consumers must die when there is nothing to consume.

@khepin @johnabil Is this not already possible? ( by setting your own Worker class extended from RabbitMQQueue::class >If i look at the octane branch and i only see an extended...