Claude Code's scheduled tasks kept firing in the hour the clocks go back, until 2.1.299

Claude Code's scheduled tasks and loops have been firing again after every turn, or firing early, during the repeated hour at the end of daylight saving time, and version 2.1.299 fixes it. Anthropic's changelog records the fix, and the release went up on npm at 00:23 UTC on October 14.

Anthropic's wording is exact:

Fixed scheduled tasks and loops firing again after every turn, or firing early, during the repeated hour when daylight saving time ends

Firing again after every turn is not the same as a job running twice. The same release also fixes the scheduling tools announcing a job for the wrong minute, so they now report each job's actual next run time.

Scheduled tasks and loops are how Claude Code runs a prompt on a timer, in a terminal session or in a cloud routine. Each extra firing is another prompt sent, and Anthropic gives no count of how many were sent or how many users saw it.

European clocks repeat an hour on October 25

European Summer Time ends at 01:00 UTC on Sunday October 25, which is 03:00 CEST becoming 02:00 CET, so the 02:00 hour runs twice in central Europe and the 01:00 hour runs twice in the UK. US daylight saving time ends a week after that, on November 1.

Anthropic names no country and no date, and claims no connection to any particular clock change. A repeated hour is a property of every one of them, and the fix landed 11 days before Europe's.

Scheduled tasks keep getting patched

Version 2.1.292 fixed several scheduled-task failures, among them saved tasks created after /resume, /branch or /clear never firing at all. Version 2.1.293 then reverted the 2.1.290 cloud-session fix that covered a pending wakeup lost when a container restarted, and 2.1.295, the release that also let a failed hook block a tool call, fixed a stopped task coming back on resume after a rewind.

Version 2.1.299 adds two more on the same machinery. Scheduled wakeups were not firing at all while a background task was running in Agent SDK, IDE and remote-control sessions, and Ultracode was not being announced to scheduled tasks or other delivered headless turns on installs that have the setting on.

Check which build you are on

On October 14 the package's stable tag still pointed at 2.1.287, according to the npm registry, which predates every scheduled-task fix listed above. A machine pinned to stable goes into the clock change with none of them.

Version 2.1.299 carries the latest tag instead, and a 2.1.300 build went up on the next channel at 14:27 UTC the same day. Neither is what an install on stable receives.

The fix itself is in 2.1.299. The hour it covers arrives at 01:00 UTC on October 25.

Note: Links to online stores in articles can be so-called affiliate links. If you buy through this link, MIXED receives a commission from the provider. For you the price does not change.