cron daemon second based issue resolved #178
Merged
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.
Problem
Second-based schedules like
everyThirtySeconds()were executing every second instead of respecting their configured intervals. A command scheduled to run every 30 seconds was triggering 30 times instead of once per interval.Root Cause
The daemon was checking isDue() every 100ms (10 times per second). When a command became "due" at a particular second, it would execute multiple times within that same second because:
Implemented proper interval-based execution tracking using React PHP Event Loop