Fix scheduled task instance mode execution and queue management #2894
+55
−5
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.
Scheduled tasks in multi-instance mode stopped executing after the queue filled up (5 tasks). Single-instance mode failed to kill old tasks before starting new ones due to missing status tracking.
Root Causes
Multi-instance mode: Fixed queue limit of 5 caused task rejection when long-running tasks accumulated (e.g., 500s tasks scheduled every minute)
Single-instance mode:
running, preventing detection of active tasksnull/undefinedas multi-instance instead of single-instanceChanges
back/shared/runCron.tsrunningon spawn,idleon exit (with error handling)allow_multiple_instances !== 1treats null/undefined as single-instanceback/shared/pLimit.tsallow_multiple_instancesper task to determine queue limitsCrontabModelat module level to avoid repeated dynamic importsOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.