Repository navigation
Conversation
sduenas
force-pushed
the
fix-lost-scheduled-jobs
branch
from
November 12, 2026 08:38
bf53e2f to
29154e0
Compare
Jobs scheduled to run immediately could be lost and never executed. RQ versions older than 3.0 add the job id to the scheduled registry before the job is stored in Redis. If the RQ scheduler reads the registry in between, it removes the id without enqueuing the job, so the job is never run and no error is reported. Jobs that must run immediately are now added to the queue directly. Jobs scheduled in the future still use the scheduled registry, because the RQ scheduler doesn't read them until they are due. Signed-off-by: Santiago Dueñas <sduenas@grimoirelab.org> Assisted-by: Claude:claude-opus-5.5
sduenas
force-pushed
the
fix-lost-scheduled-jobs
branch
from
November 12, 2026 17:48
29154e0 to
a34e6a6
Compare
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
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.
Jobs scheduled to run immediately could be lost and never executed. RQ versions older than 3.0 add the job id to the scheduled registry before the job is stored in Redis. If the RQ scheduler reads the registry in between, it removes the id without enqueuing the job, so the job is never run and no error is reported.
Jobs that must run immediately are now added to the queue directly. Jobs scheduled in the future still use the scheduled registry, because the RQ scheduler doesn't read them until they are due.
Assisted-by: Claude:claude-opus-5.5