claude-code - 💡(How to fix) Fix CCR routines fail to start — "Failed to start run" on all triggers, research preview [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#56480Fetched 2026-05-06 06:26:54
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×4commented ×2closed ×1

All Claude Code Routines fail to start with "Failed to start run" in the UI. The error appears immediately with no run logged (Runs shows "No runs yet"), so the failure is at the infrastructure level before the agent launches.

Error Message

All Claude Code Routines fail to start with "Failed to start run" in the UI. The error appears immediately with no run logged (Runs shows "No runs yet"), so the failure is at the infrastructure level before the agent launches.

Root Cause

All Claude Code Routines fail to start with "Failed to start run" in the UI. The error appears immediately with no run logged (Runs shows "No runs yet"), so the failure is at the infrastructure level before the agent launches.

RAW_BUFFERClick to expand / collapse

Description

All Claude Code Routines fail to start with "Failed to start run" in the UI. The error appears immediately with no run logged (Runs shows "No runs yet"), so the failure is at the infrastructure level before the agent launches.

Environment

  • CCR environment ID: env_01MTBZtG2wp3etCczUd5xxqb
  • Platform: Research preview (claude.ai/code)

What I tried

  • Re-authorized GitHub access
  • Deleted and recreated all three routines fresh
  • Repo (JETCharge-RnD/jc-team-os) shows as connected in the UI
  • Routines show as Active with correct schedule

Result

Every force-run attempt returns "Failed to start run. You can try again." immediately. No runs are ever logged — the failure happens before the agent launches.

extent analysis

TL;DR

The issue may be related to infrastructure or environment configuration, and verifying the CCR environment settings and GitHub connection is a potential first step.

Guidance

  • Check the CCR environment ID env_01MTBZtG2wp3etCczUd5xxqb for any configuration issues or restrictions that might be preventing the routines from starting.
  • Verify that the GitHub repository JETCharge-RnD/jc-team-os is correctly connected and authorized in the CCR environment.
  • Review the routine schedules and settings to ensure they are correctly configured and active.
  • Attempt to run a routine with a different schedule or configuration to isolate the issue.

Notes

The issue seems to be at the infrastructure level, and without more information about the CCR environment and GitHub connection, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try re-configuring the CCR environment settings and GitHub connection to see if it resolves the issue, as the problem appears to be related to the infrastructure or environment configuration.

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

claude-code - 💡(How to fix) Fix CCR routines fail to start — "Failed to start run" on all triggers, research preview [2 comments, 2 participants]