-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedule between()
not working as expected
#50120
Comments
between()
not working as expected
Hey there, Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out. Thanks! |
Laracasts user s4muel reports the bug is actually in the Should I file a bug for the artisan command? I manually converted my projects schedules into the fluent format from the hardly readable cron, and now I have no way to check if it's the same as it was. |
Hello, I have the same bug and I'm using Laravel 11.0.7 and PHP 8.3.4. This is the output after launch
This is the part of code in the route console configuration use App\Console\Commands\DataImport;
use Illuminate\Support\Facades\Schedule;
Schedule::command(DataImport::class)
->everyFiveMinutes()
->between('9:00', '23:59')
->withoutOverlapping()
->emailOutputOnFailure(config('site.default_notice_email')); |
created explicit issue about the |
Laravel Version
10.44
PHP Version
8.1.5
Database Driver & Version
No response
Description
I wanted to convert old style cron expressions into the more readable fluent method format, but noticed that the
between
method when scheduling commands seems to not be doing anything.I use the example from the docs (https://laravel.com/docs/10.x/scheduling#between-time-constraints):
And launch
php artisan schedule:list
:As you can see the configuration resolves itself to just
hourly
, is this a bug?Steps To Reproduce
add
to
app\Console\Kernel.php
and launchphp artisan schedule:list
The text was updated successfully, but these errors were encountered: