Diagnose deployment failures for Express · Ample Computer

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

You need

Exact tested configuration

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.

   $ ample logs <deployment_id> --kind build
  1. Read the runtime log. For a live-but-misbehaving app the runtime log shows the process output.
   $ ample logs <deployment_id> --kind runtime
  1. 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 --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

What it doesn’t cover