Repository navigation
fix(schedule): recheck queued carriers without waiting seven days - #8800
Closed
mzxchandra wants to merge 1 commit into
Closed
mzxchandra wants to merge 1 commit into
mzxchandra wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This branch was previously deployed
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 crashed scheduled worker can leave its occurrence claimed even after its provider run is terminal. The due-schedule filter currently waits for the maximum supported execution lifetime (seven days plus five minutes) before inspecting that carrier, so an active schedule can miss days of runs after an OOM.
Recheck claimed occurrences after five minutes without shortening their execution leases. Existing carrier reconciliation still decides whether to retain a running job, account for a terminal job, or cancel an expired one. Gate on the schedule's last update as well as its original claim so retained live carriers are not fetched on every cron tick.
Validation: 40 scheduler route tests pass, including early eligibility after a stalled claim, throttling repeated lookups, preserving a live seven-day job, and reconciling a failed provider with a log left in redacting. API validation audit and Biome checks pass.