This repository was archived by the owner on Jun 18, 2025. It is now read-only.
Scheduled jobs in the Pulse system are being incorrectly resumed after restart when their lockedAt field is set to null. #79
Conversation
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
… values instead of existence. Prevents accidental resumption or resetting of jobs that are not actively locked but happen to have a lockedAt field set to null.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 original query condition: lockedAt: { $exists: true }
matches documents where the lockedAt field exists, including those where lockedAt is null. This leads to unintended resume of jobs that are not actually locked but have a lockedAt: null field due to schema defaults or prior processing.