I like this idea 👀

@barryvdh do you have time to send a PR to Horizon, Octane, and Reverb for this? 👀

I can take a look, but do you want me to bump the requirement, or add a version/method check?

Horizon: laravel/horizon#1671
Pulse: laravel/pulse#469
Reverb: laravel/reverb#355
Octane: laravel/octane#1081

This is also very useful for development. Horizon for example needs a restart after making queue (jobs) changes and you want to test that locally.

Shouldn't schedule:interrupt be added to the default list?

Shouldn't schedule:interrupt be added to the default list?

I was not aware of the command, but yes I think so.

Shouldn't schedule:interrupt be added to the default list?

I don't think so.

Most scheduled tasks spawn separate artisan tasks, which will pick up any changes already.

Interrupting a schedule cycle doesn't "release" these tasks on a sort of queue, so some tasks would only run again on their next cycle, be it daily, monthly, or whatever.

When a user runs schedule:interrupt manually or manually adds this command to their deployment script, they are well aware of the consequences and can mitigate them consciously.

Adding it as an automatic side effect of the reload command could overshadow these caveats.

It's for Interrupting Sub-Minute Tasks.

Otherwise, an instance of the schedule:run command that is already running would continue using your application's previously deployed code until the current minute ends.