claude-code - 💡(How to fix) Fix [BUG] Cowork scheduler stops firing recurring tasks after ~24-30 hrs uptime; only Windows reboot recovers [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55631Fetched 2026-05-03 04:48:26
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×2

Error Message

Error Messages/Logs

  • No visible error to user; scheduler just goes silent

Code Example

Occurrence 1 (2026-04-29 evening → 2026-04-30 night, ~24-30 hrs)**
- Last successful fire: hourly-email-triage at 4/29 13:02 UTC
- App restart attempted: did NOT resolve
- Full Windows restart: resolved. Catch-up batch fired at 5/1 04:07 UTC.

**Occurrence 2 (2026-05-01 daytime → 2026-05-02 morning, ~24+ hrs)**
- Last successful fire: daily-brief at 5/1 12:06 UTC
- Discovered: 5/2 morning when daily-brief failed to fire at 7:06 AM CT
- Possibly correlated with: PowerShell cleanup script run Fri afternoon (cleared temp folders, restarted Windows Explorer)
- Status: Windows reboot pending

## Diagnostic notes

- `/doctor` slash-command returns "not available in this environment" in Cowork — diagnostic tooling gap between Code CLI and Cowork desktop
- No visible error to user; scheduler just goes silent
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The Claude desktop app's scheduled-task scheduler stops firing recurring (cron-based) tasks after some indeterminate uptime period. One-time fireAt tasks scheduled within the stall window also fail to fire. Restarting the Claude app does NOT recover. Only a full Windows OS reboot resets the scheduler.

What Should Happen?

Recurring scheduled tasks should fire reliably on their cron schedule for the lifetime of the user's session. The scheduler service should:

(a) self-heal if it stalls — a watchdog that detects missed firings and recovers without requiring a Windows reboot (b) surface errors to the user when stalls do happen, rather than failing silently (c) recover via app restart at minimum — full OS reboot should not be required (d) provide diagnostic logging users can access (logs from the scheduler service, missed-fire events queued for catch-up)

A user with 60+ scheduled tasks should be able to depend on them firing within a few minutes of their scheduled time, every time, for as long as the app is running.

Error Messages/Logs

Occurrence 1 (2026-04-29 evening → 2026-04-30 night, ~24-30 hrs)**
- Last successful fire: hourly-email-triage at 4/29 13:02 UTC
- App restart attempted: did NOT resolve
- Full Windows restart: resolved. Catch-up batch fired at 5/1 04:07 UTC.

**Occurrence 2 (2026-05-01 daytime → 2026-05-02 morning, ~24+ hrs)**
- Last successful fire: daily-brief at 5/1 12:06 UTC
- Discovered: 5/2 morning when daily-brief failed to fire at 7:06 AM CT
- Possibly correlated with: PowerShell cleanup script run Fri afternoon (cleared temp folders, restarted Windows Explorer)
- Status: Windows reboot pending

## Diagnostic notes

- `/doctor` slash-command returns "not available in this environment" in Cowork — diagnostic tooling gap between Code CLI and Cowork desktop
- No visible error to user; scheduler just goes silent

Steps to Reproduce

Tasks affected: ALL recurring (e.g., daily-brief, hourly-email-triage, eod-triage, daily-crypto-brief, weekly-market-context-sunday, crypto-price-alerts)

  • One-time tasks scheduled within the stall window also fail to fire
  • After Windows reboot: recurring tasks catch-up-fire (multiple at once) and resume normal cadence
  • Restarting just the Cowork/Claude app is NOT sufficient — must be full OS reboot

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The scheduler service in the Claude desktop app may need a watchdog mechanism to self-heal and recover from stalls without requiring a Windows reboot.

Guidance

  • Investigate the implementation of the scheduler service to identify potential causes of stalls, such as resource leaks or infinite loops.
  • Consider adding a watchdog mechanism to detect missed firings and trigger a recovery process.
  • Implement diagnostic logging to surface errors and provide users with accessible logs to troubleshoot issues.
  • Review the PowerShell cleanup script run on Fridays to determine if it's correlated with the scheduler stalls.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The issue lacks information on the specific implementation of the scheduler service, making it challenging to provide a definitive solution. Further investigation is required to determine the root cause of the stalls.

Recommendation

Apply a workaround by implementing a watchdog mechanism to detect and recover from scheduler stalls, as a full fix may require significant changes to the scheduler service.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING