CCR scheduled triggers hang indefinitely — no output produced

Resolved 💬 3 comments Opened Apr 14, 2026 by kpmrozowski Closed Apr 18, 2026

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.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗