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

_chris's avatar

Does forge call schedule:run automatically?

I am a little confused. Initially in my forge server I added the schedule:

php /home/forge/default/artisan schedule:run

for every minute and my commands were running twice. I've now removed it so the only command visible in forge is

/usr/local/bin/composer self-update

But my commands are still running (now thankfully once).

This is fine, I guess I am just looking for confirmation that forge is running the scheduler automatically or I am doing something wrong?

EDIT: Ok I did a little more digging and it looks like there is something up. I set up an identical site in forge (using digital ocean), didn't add the schedule:run job and nothing was coming through (I have a schedule set up to email me every minute as a test).

So I added the schedule:run job and the emails started to come through. Then I removed it and they stopped.

So it looks like somehow one of my forge sites is running the schedule in the background and one of them isn't.

Can anyone guide me on how to dig into this a little deeper?

Thanks

0 likes
3 replies
_chris's avatar

Nobody have any insights here?

livingos's avatar

For the scheduler to run you need to use forge to run it.

In Forge you add to a server in the Scheduler page. Something like:

php /home/forge/yourfolder.com/current/artisan schedule:run

set to run every minute.

Then in your laravel app source code you specify the jobs you want to run in Console/Kernal.php

_chris's avatar

Yeah exactly, what I'm saying is that my schedule:run command is being triggered even without that from job. I think I'm going to spin up a new server and start again.

Please or to participate in this conversation.