If you see laravel has a priority system for queues so for the first issue that you had that you don't want simultaneous execution just set up one priority with only one worker.

And laravel will process one job one by one

If you want a1 and the b1 and then b2 you just need to say ok when a is done dispatch the job b1 and so one

It's possible to dispatch jobs inside jobs just use the dispatches jobs trait

For the case that b1 fails I suggest to capture the possible exceptions In the code so b2 can be executed

arasmit2453 said:

If you want a1 and the b1 and then b2 you just need to say ok when a is done dispatch the job b1 and so one

It's possible to dispatch jobs inside jobs just use the dispatches jobs trait

For the case that b1 fails I suggest to capture the possible exceptions In the code so b2 can be executed

This couples them. Can't i use after handler like I intended?