Repository navigation
fix(schedule): give a recurring event of the laravel driver its interval - #477
Merged
ogorzalka merged 1 commit intoOct 14, 2026
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A recurring event placed with the
laraveldriver ran once and was then forgotten when the caller gave only the name of its recurrence, which is what the fluent API (Schedule::event('x')->hourly()) and#[Schedule]do. Only WordPress's ownwp_schedule_event()also passes the interval.LaravelQueueDriver::placeIdentified()sent the event as it was, soRunScheduledEvent::conclude()saw no interval and removed the entry instead of queuing the next occurrence.recurring()already looked the interval up fromwp_get_schedules(); both paths now sharewithInterval().Found live on a throwaway project on the release head (framework dev-release/v13.36.0, schedule 0.1.3, hook 2.0.0, Laravel 13.36.0): fluent API, a bare
Eventand a#[Schedule]in a theme did not come back after their first run; with the fix all three are queued again about an hour later (3586 s), likewp_schedule_event()and the Action Scheduler driver already did.Test: a recurring event with no interval gets its job's interval and queues its next occurrence. Schedule tests 42 passed, PHPStan, Rector and Pint clean.