> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vendo.run/llms.txt
> Use this file to discover all available pages before exploring further.

# E-LIVE-004

> Retired: doctor no longer reads the configured execution venue from /status.

```text retired theme={null}
E-LIVE-004 — retired, doctor no longer emits this code
```

`error_code: E-LIVE-004` · `status: retired`

## What you're seeing

Nothing: `npx vendo doctor` cannot print this code anymore. You are reading
it from an older run's output, or a saved report.

## Why

This warning fired when the live `/status` route reported no execution venue
at all. Doctor reads your files now and never asks the running app what it
composed, so it cannot tell which venue you ended up with.

## The fix

The gap is still real, and you check it yourself now. Read your `createVendo`
call. If the `sandbox` slot is unset and `VENDO_API_KEY` is not in your
server environment, you have no venue: tree-only apps render fine, and any
app that needs a server (rungs 2 through 4) answers `sandbox-unavailable`.

Set `VENDO_API_KEY` and Vendo fills the sandbox slot with the managed Cloud
sandbox, no `sandbox` option needed.

```bash theme={null}
export VENDO_API_KEY=vnd_live_...
```

Or pass your own adapter, for example `sandbox: e2bSandbox()`, which reads
`E2B_API_KEY` as its credential.

## Related errors

* [E-CLOUD-001](/production/troubleshooting/e-cloud-001) — `VENDO_API_KEY` set but not usable, which doctor still catches
* [E-TURN-001](/production/troubleshooting/e-turn-001) — the model seat, filled by the same key