Repository navigation
docs: Describe scheduling while a job is running - #43
Merged
Merged
Conversation
The README only covered the pending case: schedule the same identifier twice and the earlier due date wins. That silently leaves out the case a caller is far more likely to get wrong, and it reads as if it were the whole rule. A scheduled job may run for minutes or hours. Anything scheduling the same identifier during that run does so because the basis the job computed from has changed, so the newer schedule has to outlive the finished run. Behaviour unchanged; ReschedulingClaimedTest already pins it down.
paxuclus
approved these changes
Sep 14, 2026
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
2 participants
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.
The README only covered the pending case: schedule the same identifier twice and the earlier due date wins. That silently leaves out the case a caller is far more likely to get wrong, and it reads as if it were the whole rule.
A scheduled job may run for minutes or hours. Anything scheduling the same identifier during that run does so because the basis the job computed from has changed, so the newer schedule has to outlive the finished run.
Behaviour unchanged; ReschedulingClaimedTest already pins it down.