The whole hunk
from line 630, old and new numbered
/
lines
from line 630
630630
631631## Session start errors
632632
633Session start errors appear before any work begins. Some are transient and clear on retry; the rest point to capacity or environment configuration rather than credentials.
633Session start errors appear before any work begins. Some are transient and clear on retry; the rest point to capacity or environment configuration.
634634
635635### Still waiting for available capacity
636636
from line 642
642642
643643**What it means**
644644
645Compute capacity is temporarily busy. The session starts on its own once capacity frees up.
645The session was created and is still waiting for compute to run it. Why it waits differs between Anthropic-hosted and self-hosted [environments](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope).
646646
647On an Anthropic-hosted environment, capacity is temporarily busy or the session is taking longer than usual to start, and the session normally starts on its own. If it never starts, Claude posts the [Session failed to start](#session-failed-to-start-the-session-container-never-connected) message instead.
648
649On a [self-hosted environment](https://code.claude.com/docs/en/self-hosted-environments), no runner has claimed the session yet. The session waits in the environment's queue until a runner claims it.
650
647651**How to resolve**
648652
649Wait; no action is needed. Users should reply in the same thread if they have more to add, since starting a new thread only queues a second session behind the first.
653On an Anthropic-hosted environment, wait; no action is needed.
654
655On a self-hosted environment, use [Troubleshooting](https://code.claude.com/docs/en/self-hosted-environments-deploy#troubleshooting) in the self-hosted environments guide to find out why no runner is claiming the session. The queued session starts once a runner claims it.
656
657Either way, users should reply in the same thread if they have more to add, since starting a new thread only queues a second session behind the first.
650658
651659### Session failed to start: the session container never connected
652660