Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix CCR scheduled triggers hang indefinitely — no output produced [1 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#47921•Fetched 2026-04-15 06:38:34
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
kpmrozowskikpmrozowski
Participants
github-actions[bot]github-actions[bot]kpmrozowskikpmrozowski
Timeline (top)
labeled ×3commented ×1

Scheduled trigger runs (CCR sessions) spin indefinitely showing status words ("Accomplishing...", "Whirring...", "Enchanting...", etc.) but never produce any output. The agent never starts executing — no text, no tool calls, nothing.

Root Cause

Scheduled trigger runs (CCR sessions) spin indefinitely showing status words ("Accomplishing...", "Whirring...", "Enchanting...", etc.) but never produce any output. The agent never starts executing — no text, no tool calls, nothing.

RAW_BUFFERClick to expand / collapse

Bug Report: CCR Scheduled Triggers Hang Indefinitely

Description

Scheduled trigger runs (CCR sessions) spin indefinitely showing status words ("Accomplishing...", "Whirring...", "Enchanting...", etc.) but never produce any output. The agent never starts executing — no text, no tool calls, nothing.

Environment

  • Account: Kornel Mrozowski
  • Environment ID: env_01Pp2vZS5KCW1htGkx8PrNRN
  • Platform: claude.ai/code (web)

Trigger IDs

  • trig_01N7aGrsnotB4At9C82UGJEP — "Mattermost Daily Digest" (real workload)
  • trig_012AtmoG6kPgcw4Micq7sW6p — "CCR Test - Hello World" (trivial test: "Say hello, then run: ls -la")

Session IDs that hung

  • session_0154VGbtRwSaXdN4ZnpY3DyK (1:40 PM, marked "completed" but empty)
  • session_01XW2FTUMwTnmM7zgojVQ6Eu (2:45 PM, hung)
  • session_01HewnLP8VqLmtgGLSpJwzSW (2:59 PM, hung)

Reproduction Steps

  1. Create any scheduled trigger with a git repository source
  2. Click "Run now"
  3. Session opens, shows rotating status words
  4. No output is ever produced — agent never starts

What was tried

  • Switched model from claude-opus-4-6 to claude-sonnet-4-6 — same result
  • Simplified prompt to trivial "Say hello" — same result
  • Added GitHub PAT to git URL for private repo auth — same result
  • Created a brand new trigger from scratch — same result

Expected behavior

The CCR agent should clone the repo and begin executing the prompt, producing visible output in the session.

Actual behavior

The session spins indefinitely with no output. The UI shows random status words ("Accomplishing...", "Moseying...", "Coalescing...", etc.) but the agent never produces any text or makes any tool calls. Some sessions eventually get marked "completed" (green check) despite having zero content.

extent analysis

TL;DR

The issue can be mitigated by investigating the Git repository source and its accessibility, as the CCR agent fails to clone the repository and execute the prompt.

Guidance

  • Verify the Git repository source URL and its authentication settings to ensure the CCR agent can access the repository.
  • Check the repository's size and complexity to determine if it's causing the cloning process to hang.
  • Test the trigger with a public repository to isolate the issue and determine if it's related to private repository authentication.
  • Investigate the CCR agent's logs to see if there are any error messages or clues about what's causing the hang.

Example

No code snippet is provided as the issue seems to be related to the CCR agent's interaction with the Git repository.

Notes

The issue may be related to the CCR agent's ability to clone the Git repository, and investigating the repository's accessibility and size may help resolve the issue. Additionally, testing with a public repository can help determine if the issue is related to private repository authentication.

Recommendation

Apply workaround: Investigate and resolve any issues with the Git repository source and its accessibility to allow the CCR agent to clone the repository and execute the prompt. This is recommended as the issue seems to be related to the repository and not the CCR agent itself.

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 CCR agent should clone the repo and begin executing the prompt, producing visible output in the session.

#embedding generation#cache error#pipeline error#runtime error#dependency conflict

Still need to ship something?

×6

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

Back to top recommendations

TRENDING