Claude Code Scheduled Tasks Bug: Silent Failures and False Success Reports
wshallwshall · ghdev · 2026-07-31
A developer reported a critical bug in Claude Code's scheduled-tasks feature. Six sessions attempting to schedule a restart after hitting usage limits all failed in two distinct ways:
- Silently dropped: 3 tasks were never dispatched but remained enabled: true with a nextRunAt timestamp stuck in the past, leaving them permanently armed.
- Killed mid-execution but reported success: 3 tasks were killed mid-tool-call within 15-27 seconds, but the system marked them as enabled: false with lastRunAt set—identical to a successful completion.
The report notes that the underlying scheduling API functions correctly, suggesting the defects lie entirely in dispatch, execution, and state reporting. Additionally, when multiple tasks share the same fire time, only a prefix of the tasks is dispatched while the rest are dropped.
More from coding & agent
- Connected steps are not a workflow: nobody designs the handoff — usehive · 2026-10-16
- Making Blender animations with Opus, Astra and Argon: how you prompt still matters — chongdashu · 2026-10-16
- Running PolyStrata + Cline coding agent on a $0-fancy laptop at ~90 tok/s — rpwoerk · 2026-10-16
- How do you attribute agent gains: model training or infrastructure? — jrxna · 2026-10-16
- Feed Claude your books, blogs and top engineers' code for claude.md — 'it now writes better code than me' — blaizedsouza · 2026-10-16
- Open-source /label plugin auto-names and colors Claude Code sessions in one step — hermanschutte · 2026-10-16