[BUG] Claude Code routine task did not fire at scheduled time

Resolved 💬 1 comment Opened May 12, 2026 by cbl-caravelo Closed Jun 11, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] 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_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗