Decouple scheduler scan from execution dispatch#124
Merged
charlesrhoward merged 1 commit intomainfrom Feb 16, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
charlesrhoward
deleted the
codex/issue-114-decouple-scheduler-dispatch
branch
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.
Summary\n- collect due scheduler tasks first during each tick\n- dispatch due tasks without awaiting each task serially\n- keep per-task error logging for asynchronous dispatch failures\n\nCloses #114
Note
Medium Risk
Changes scheduler execution semantics from serial to concurrent dispatch, which can alter timing and increase parallel load; errors are now handled asynchronously and rely on logging for visibility.
Overview
During each
schedulerTick, the scheduler now collects due tasks first and then dispatchesrunTask(..., 'cron')asynchronously (fire-and-forget) rather than awaiting each run inline.Async dispatch failures are now caught per task and logged via
scheduler.tick.run_task_failed, allowing the tick to complete quickly while still surfacing per-task errors.Written by Cursor Bugbot for commit 6837fe6. This will update automatically on new commits. Configure here.