[BUG] CCR trigger stuck in 'setting up container' for 2+ days, no way to cancel

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

A remote scheduled trigger (CCR) has been stuck in the "Cloud Container wird eingerichtet" / "setting up container" state for over 48 hours without making any progress or timing out.

Trigger ID: trig_011grenf4V9cPifb9qfqVgTA
Run started: ~2026-04-24 15:50 UTC
Environment: env_01GJo4Ex3fkwjx7RbDSPsK1j (Default, anthropic_cloud)

Expected behavior: The container should start within a few minutes, execute the agent, and complete.

Actual behavior: The job has been in "setting up container" for 2+ days with no progress, no error, and no automatic timeout.

Additional issue: There is no way to cancel or stop a running trigger job — neither via the dashboard nor via the API (RemoteTrigger only supports list, get, create, update, run). A cancel/stop action for running jobs is missing.

Workaround tried: Disabled the trigger to prevent further scheduled runs. The stuck job remains unresolvable from the user side.

What Should Happen?

Container gets create and job runs.

Error Messages/Logs

Steps to Reproduce

See instructions / code with the referenced trigger ID.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_