CCR routine stuck on 'Setting up a cloud container' indefinitely

[danielportuondo]

Description

A Claude Code remote routine (CCR) is getting stuck on 'Setting up a cloud container' and never progresses. The run hangs indefinitely (25+ minutes observed) without any error message or timeout.

Routine details

• Routine ID: trig_01VWavCCKQ9RNJF77Aqv43ns
• Environment ID: env_01FQfppgarxY7VNde2qkxJdg (anthropic_cloud)
• Model: claude-opus-4-7
• Schedule: Every 3 hours (0 */3 * * *)
• Repo: Private GitHub repo (authenticated via PAT in git URL)

Steps to reproduce

1. Create a CCR routine with a private GitHub repo source using a PAT-authenticated URL
2. Click "Run now" from the routines page (https://claude.ai/code/routines)
3. Observe the run status stays on "Setting up a cloud container" indefinitely

Expected behavior

Container provisions within ~1-2 minutes and the agent begins executing.

Actual behavior

Stuck on "Setting up a cloud container" for 25+ minutes with no progress, no error, and no timeout. The routine config has been verified correct (PAT authenticates, repo is accessible, all fields valid).

Additional context

• Verified the PAT can authenticate and clone the repo successfully from local machine
• The main branch contains all required code (PR was merged before attempting to run)
• This occurred on both manual "Run now" triggers
• No error message is shown — the UI just stays on the loading state indefinitely

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] CCR scheduled routines stuck at "Setting up a cloud container" since 2026-04-24 #53691
2. [BUG] CCR trigger stuck in 'setting up container' for 2+ days, no way to cancel #53470
3. Code Routines: cron fires but cloud containers never execute prompts (silent failure with ended_reason: run_once_fired) #54260

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[0xbrainkid]

This is a provisioning-state legibility failure.

If a CCR routine sits indefinitely on Setting up a cloud container, the operator is trapped in a state that looks active but provides no trustworthy signal about whether work is blocked, still progressing, or orphaned behind the scenes.

That matters because provisioning is not just a loading phase — it is the step where users decide whether to wait, retry, or abandon the attempt. Indefinite limbo destroys that decision boundary.

I would want clarity on:

1. whether the container creation is actually stalled, retried silently, or waiting on an upstream resource lock
2. whether any server-side artifact exists that the user can inspect or kill while the UI remains stuck
3. whether the product can distinguish slow provisioning from dead provisioning and surface that difference clearly

A long-running setup step needs explicit progress semantics or failure semantics. Otherwise the user is paying time and trust into a black box with no bounded outcome.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.