fix: clear recovery state on requeue_task#2
Conversation
…tasks requeue_task removed the task from the dispatched set and approved preflight, but never cleared the recovery failure counter. Tasks that hit max retries (retryable: false) could never be re-dispatched even after the underlying issue was fixed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PR SummaryLow Risk Overview Threads a new Written by Cursor Bugbot for commit 77bd03c. This will update automatically on new commits. Configure here. |
Add TestRequeueTask class verifying clear_recovery_callback is invoked on requeue, and that requeue works without it. Add info-level log when recovery state is cleared. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
requeue_task(supervisor MCP tool) removed the task from the dispatched set and approved preflight, but never cleared the recovery failure counterretryable: false) could never be re-dispatched even after the underlying issue (e.g. missing repo config) was fixedrecovery.clear()to reset the failure counter, allowing the task to be picked up on the next pollContext
QR-273 failed 3 times with "No repos configured" (config issue since fixed). After
requeue_task, the orchestrator still refused to dispatch it because recovery state hadretryable: false.Test plan
requeue_taskclears recovery state by requeueing a previously-failed task🤖 Generated with Claude Code