Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] [Routines] Scheduled run stuck in "En cours d'exécution" for 2+ days (zombie execution)

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 message visible. The run shows "En cours d'exécution" (running) indefinitely with no output, no error, and no cancel button in the

Code Example

No error message visible. The run shows "En cours d'exécution" (running) 
indefinitely with no output, no error, and no cancel button in the 
Routines execution history panel.
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?

<img width="1433" height="1063" alt="Image" src="https://github.com/user-attachments/assets/672bd745-98c4-4b24-8012-8baf189ea6e2" />

Bug report

A scheduled Routine run has been stuck in "En cours d'exécution" (running) state since April 18, 2026 at 14:05 UTC+2. It never completed or timed out.

Steps to reproduce

  1. Create a daily Routine running at 14:00 UTC+2
  2. Observe the April 18 execution — it never terminated
  3. The run still shows "En cours d'exécution" 2 days later

Expected behavior

The run should either complete (success/failure) or timeout after a reasonable duration.

Actual behavior

The execution is permanently stuck in "running" state with no way to cancel it from the UI. Subsequent runs (April 19, April 20) completed successfully, so the zombie run does not block new executions, but it may consume usage quota.

Environment

  • Platform: Claude.ai web (Routines)
  • Run type: Programmé (scheduled)
  • Routine: remote ("À distance")

What Should Happen?

The scheduled Routine run should complete (success or failure) within a reasonable time, or timeout automatically. A cancel/stop button should be available in the UI to terminate a stuck run manually.

Error Messages/Logs

No error message visible. The run shows "En cours d'exécution" (running) 
indefinitely with no output, no error, and no cancel button in the 
Routines execution history panel.

Steps to Reproduce

  1. Create a daily scheduled Routine on claude.ai web (Routines feature)
  2. Let it run — if the execution hangs, it enters an infinite "running" state
  3. Navigate to Routines → execution history
  4. Observe: the stuck run shows "En cours d'exécution" with no cancel button
  5. Subsequent scheduled runs complete successfully, but the zombie run remains stuck indefinitely (confirmed: 2+ days stuck)

Note: closest related issue is #40534 (different feature, same hang pattern)

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.3561.0 (fbc74b)

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

Claude Desktop

extent analysis

TL;DR

The scheduled Routine run is stuck in a "running" state due to an unknown issue, and a potential workaround is to investigate and potentially modify the routine's configuration or the underlying system to allow for proper timeout or cancellation.

Guidance

  • Investigate the routine's configuration and the system's timeout settings to see if there's a misconfiguration that's causing the routine to hang indefinitely.
  • Check if there are any system or network issues that could be preventing the routine from completing or timing out.
  • Consider reaching out to the developers or support team to see if there's a known issue with the Opus model or the Claude Code version 1.3561.0 that could be causing this problem.
  • Review the related issue #40534 to see if there are any similarities or potential solutions that could be applied to this case.

Notes

The lack of error messages or logs makes it difficult to determine the root cause of the issue, and the fact that subsequent runs complete successfully suggests that the problem may be specific to this particular routine or execution.

Recommendation

Apply workaround: Since the issue is unclear and there's no clear indication of a regression or a fix in a later version, the best course of action is to try to work around the issue by investigating and modifying the routine's configuration or the underlying system.

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…

FAQ

Expected behavior

The run should either complete (success/failure) or timeout after a reasonable duration.

#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] [Routines] Scheduled run stuck in "En cours d'exécution" for 2+ days (zombie execution)