Send notification after all instances of a job completes

As far as I know it's not possible to monitor it like that. However there are multiple ways in which you can fix this.

It might not be the best solution, but I currently can't think of a better solution. Let's say after each job you simply fire an event that keeps a counter with the completed jobs. You can then have a scheduled task that checks every minute if all jobs are completed by checking the counter. If that is in this case you reset the counter and you then know if this is done. You can also keep a counter for each day that you run those 10 jobs. I hope you get the idea.

You can use job events for that: https://laravel.com/docs/5.5/queues#job-events

This might help as well: https://laracasts.com/discuss/channels/laravel/what-is-the-best-way-to-show-progress-of-queue-to-user

@bobbybouwmann I was interested by your counter approach that i implemented with a table and queue event as per below :

    Queue::after(function (JobProcessed  $event) {

        switch ($event->job->resolveName()) {

            case "App\Jobs\JobVideo":
                $commandLog = CommandLog::where('command', VideoProcess::$name_command)->where('status', 'started')->latest()->first();
                if (!empty($commandLog)) {
                    $commandLog->job_current = $commandLog->job_current + 1;
                    if ($commandLog->job_current >= $commandLog->job_max) {
                        $commandLog->status = "Completed";
                    }
                    $commandLog->save();

                default:
                    break;
                }
        });

But i notice that with more than 100 jobs on different workers, randomly i dont get my job_current incremented even if all jobs are successfully done (which means while all my jobs succeed, in my table some are missing as the job_current stay < to job_max)

So i feel :

• all jobProcessed event might not be all fired
• or my table column job_current cant handle potentially simultaneous update of some jobs completing in same time

What could be the reason?

@Dave97 It's probably the second reason! You can however add a lock on writing to the database. You need to try this out. Not sure what else you have in your application that could cause this!

Documentation: https://laravel.com/docs/5.6/queries#pessimistic-locking

@bobbybouwmann Yes, i decided to implement a shared lock...

but i still often have the last job which doesnt increment my db, as if the last job was not all the time firing the Queue::after JobProcessed or JobFailed listener that im using for incrementation (sometimes it does so the code must be ok).

I have 100 http call so 100jobs with 20 workers. It is kind of surprising to see the 50 first jobs are done within 2s then for the next ones, the lengh of time increase progressively until 50s. But they are all done despite the fact that it randomly doesnst increment the last one in db.

I am not familiar with using shared lock: What happen when a job try to update a row of db locked by another job, does it wait or does it fail? This answer could help me to understand what happen....

I tried also another approach with Queue:size and subscriber https://laracasts.com/discuss/channels/laravel/queuesizequeuename-always-return-null

But i keep having Queue:size = 0, does someone has a clue for this?