Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hey everyone, I'm working on the Laravel 8 application. It's a multi-tenant application, where store owners register and sell their products. The application is working fine, but I've added Queue jobs for Order Notification. when a user places an order, in the backend we trigger an event and there is an event listener that triggers email notifications for Jobs. This method works, properly. The issue is I hosted this application in Cpanel, in the terminal I executed the command "PHP artisan queue: work". Then the application works fine, and email notifications trigger properly, sometimes these jobs are added to the DB jobs table, but those jobs not triggering automatically. then again I execute a command in the terminal then the queued jobs from the db table are triggering. then after a week again stopped. I don't know which scenario it stopping. there is nothing in the logs. I have gone through many blogs some say to increase memory_limit, and some advised to run commands like "php artisan queue: work --daemon --sleep=3 --tries=3 --timeout=300 --memory=1000" . but none of them working, after somedays again jobs stopped and all left in jobs table.
Could anyone help me to fix this, as I said earlier it's a multi-tenant application. so customers keep questioning me for not fixing this issue. they are not getting emails properly, because jobs trigger emails
Your best option is to use for example a VPS with supervisord to run the queue worker process in the background. Alternatively you can try to use a cron job to run laravel scheduler every minute and start the queue worker in the scheduler. I've seen people using this as a solution when they can't use supervisord. Personally I always host Laravel projects on a VPS.
@gych Thanks for the reply bro. many of them suggested that method. but I'm thinking of adding cronjobs will make the application a bit slower, so I'm looking for an alternate solution. If I can't find anything else I will go with cronjobs
@rajkumar_zuan No problem, you just have to add a single cron job to run the scheduler which is not going to slow down your application. Its also instructed in the Laravel docs to add this cron job to run the Scheduler every minute. A lot of applications use it to run tasks at specific times. I also use it in some applications to start jobs at specific times. https://laravel.com/docs/11.x/scheduling#running-the-scheduler
Please or to participate in this conversation.