claude-code - 💡(How to fix) Fix [BUG] Claude Code routine task did not fire at scheduled time

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…

Error Message

Error Messages/Logs

No error shown. lastRunAt was unchanged after the scheduled time passed. nextRunAt jumped to the following week automatically.

Code Example

No error shown. lastRunAt was unchanged after the scheduled time passed. nextRunAt jumped to the following week automatically.
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?

Scheduled task (Claude Code routine) set for 15:45 local time (Barcelona, CEST UTC+2) Claude Code desktop app was open Task did not fire — lastRunAt unchanged, nextRunAt skipped to next week

What Should Happen?

Routine task should have run at the scheduled time.

Error Messages/Logs

No error shown. lastRunAt was unchanged after the scheduled time passed. nextRunAt jumped to the following week automatically.

Steps to Reproduce

  1. Create a scheduled routine via Claude Code desktop (Windows 11)
  2. Set it to run at a specific local time (e.g. 15:45 CEST / Barcelona, UTC+2)
  3. Keep Claude Code desktop app open at that time
  4. Observe: task does not fire, lastRunAt unchanged, nextRunAt skips to next week

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Claude 1.6608.2

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

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