# Diagnose deployment failures for Express

Diagnose a failed Express deployment on Ample. Deploy is synchronous: a build failure returns `build_failed` with the deployment id, and ample logs expose the build log and then the runtime log so the cause is read, not guessed.

Verified November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

## You need

- A deployment id from a failed ample deploy  
- An Ample account token with servers:read

## Exact tested configuration

```shell
build printf 'ample-build-failure-probe' >&2 && false
install npm install
runtime node
sizes - 1vcpu - 1gb
start npm run start
template node-22
```

## Steps

1. **Read the failure code.** Exit 1 with `build_failed` means the isolated build failed; exit 2 means a required preflight action is blocking.

2. **Read the build log.** The last lines name the failing command.

```shell
   $ ample logs <deployment_id> --kind build
   ```

3. **Read the runtime log.** For a live-but-misbehaving app the runtime log shows the process output.

```shell
   $ ample logs <deployment_id> --kind runtime
   ```

4. **Fix and redeploy once.** Change the source or the command override, then run ample deploy again. Do not loop deploys to poll status.

## How it was checked

✓ build log contains the failing command output· manual → “ample logs <deployment_id> --kind build shows the failure line”

## Evidence

1. November 5, 2026 · canary run  
   An intentionally failing build was rejected synchronously with `build_failed` and the failure line was readable in the build log.

2. November 6, 2026 · canary run  
   Express app with npm install and npm run start deployed on the node-22 template; the public URL served the expected response.

## Tested examples

- **Intentional build failure canary.** A failing build command is rejected synchronously and its stderr line appears in the build log.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
- Diagnosis is reading the logs: `ample logs <deployment_id> --kind build` and `--kind runtime`.
