# SandboxStarting

> The request needs the Sandbox's container, which is not running yet. A stopped Sandbox is started by the request itself; the answer carries Retry-After.

Source: https://nodus-platform-site.pages.dev/docs/reference/errors/sandbox-starting/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

<!-- Code generated by tools/errgen. DO NOT EDIT. -->

**HTTP status:** 503 · **Retryable:** yes

The request needs the Sandbox’s container, which is not running yet. A stopped Sandbox is started by the request itself; the answer carries Retry-After.

## Message

```text
sandbox "{name}" is starting
```

## What to do

retry after the Retry-After interval, or run `nodus wait sandbox/{name} --for=condition=Ready`

## On the wire

The response is a Kubernetes `Status` with `reason: SandboxStarting` and `code: 503`, plus `fix`, `docs` (this page) and `requestId`. `details.causes` lists the fields involved, when there are any. The CLI prints the fix and the request id; the Python SDK raises `nodus.errors.SandboxStarting`.