Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Inquisitive's avatar

Horizon Not working in Laravel Forge

Its Working fine local, however on dev forge, the queue is never getting triggered.

My env has:

QUEUE_CONNECTION=redis

I have tested successfully redis-cli ping and received PONG

Also, https://example.com/horizon working fine and showing the status active.

I have created a queue and also created a daemon, however on dispatching the job it is not getting fired. However, if I keep running php aritsan quueu:work --tries=3, it is starting the queue process as soon as the job is dispatched.

Here are the screenshots of queues and daemons.

https://ibb.co/Vq1NJs6

https://ibb.co/MZfFGkX (daemon, one for live and another for dev)

0 likes
5 replies
click's avatar

Update, I forgot, Laravel Horizon has its own restart command but the concept and reason is similar as I described below see the documentation https://laravel.com/docs/9.x/horizon#deploying-horizon

php artisan horizon:terminate

Did you try restarting your daemon queue and clearing your config cache php artisan config:clear?

Each time you do a new deployment you should start your queue as otherwise your queue will not pick up any code changes or any config changes.

php artisan queue:restart 

From the docs:

Remember, queue workers are long-lived processes and store the booted application state in memory. As a result, they will not notice changes in your code base after they have been started. So, during your deployment process, be sure to restart your queue workers. In addition, remember that any static state created or modified by your application will not be automatically reset between jobs.

https://laravel.com/docs/9.x/queues#queue-workers-and-deployment

Inquisitive's avatar

@click Actually i am using this queue to dump csv to database, and i got the error, as it is trying to find this file in example.com instead of exampledev.com, could daemon have something to do with it or what I could be doing wrong here?

click's avatar
click
Best Answer
Level 35

@Inquisitive please try restarting your horizon and clearing your config cache as mentioned above. If you have configured something in your .env it might be related.

Please or to participate in this conversation.