Support the ongoing development of →
Requests Queues
Last updated 1 year ago.

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.

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.

Hopefully they include the changes as I found someone else having the same issue with long running jobs.


Last updated 1 year ago.

Sign in to participate in this thread!

Full Stack Europe

Your banner here too?


We'd like to thank these amazing companies for supporting us

Your logo here?

The Laravel portal for problem solving, knowledge sharing and community building.

© 2023 - All rights reserved.