fix(cron): correct nextRunAtMs calculation for past times#1
Open
fix(cron): correct nextRunAtMs calculation for past times#1
Conversation
Fixes openclaw#10035 When creating a cron job with a time that has already passed today, the nextRunAtMs was incorrectly calculated as one year in the past. This fix detects when the calculated time is more than 24 hours in the past and forces recalculation from the current time. Tested with Asia/Shanghai timezone jobs scheduled for 07:30 and 08:00.
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.
Fixes openclaw#10035
Summary
When creating a cron job with a time that has already passed today, the nextRunAtMs was incorrectly calculated as one year in the past (2025 instead of 2026), causing the job to never run.
Changes
Testing