The first thing you could try is just increasing the timeout when posting the job onto the queue. But yes, Iron wants you to delete job before it is done. That only becomes a problem if you think the job could fail afterwards.
Last updated
1 year ago.
Solution
Thanks @andrewryno. I did just that. I couldn't find an easy way to pass in the timeout, so I submitted a pull request to add that functionality in. Fixes the issue for me, no more multiple jobs showing up.
https://github.com/laravel/framework/pull/3555
Hopefully they include the changes as I found someone else having the same issue with long running jobs.
Jay
Last updated
1 year ago.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast