Logs and health

App status

Deploying

A release is queued or building. It is not live yet.

Healthy

The latest Production release is live.

Asleep

The app is idle and will start on the next visit. See sleep when idle.

Waking

A visit is starting the app.

Failed

The latest release did not become healthy. Read its logs.

Paused

The app has been paused and is not serving.

Needs configuration

Something is missing before the app can run, often a variable.

Build and runtime logs

Select a release in the Deployments tab to follow its progress and read its logs. Read the build output first when a build fails; read the runtime logs when the app built but did not start or stay running.

Agents read logs with the MCP logs tool. It returns redacted, size-bounded output with Aozumi's diagnosis, defaults to Production, and accepts another environment.

Common failures

Aozumi reads the logs of a failed release and adds a diagnosis when it recognises the cause:

A required secret may be missing

Add the variable named in the log, then deploy again.

The app did not stay running

Check the start command and listen on PORT. Do not hard-code port 3000.

The health check did not pass

Bind to PORT, start within the grace period, and return a 2xx response from the health endpoint.

The runtime was stopped

A stop request, not a build failure: pause, replacement or idle sleep. Redeploy if the app should be running.

Health checks and history

Before a new release takes traffic, it has to become healthy; until then the previous release keeps serving. After that, Aozumi checks live apps through its gateway every few minutes and keeps 30 days of health history, which the app's health view shows next to recorded visitor traffic.

Incidents and notifications

New Production incidents, and their recoveries, appear in your workspace inbox with a link to the affected app and release. Each member marks them read separately. Notifications are in the console only; there is no email or webhook delivery yet.

Questions

Where are my app's logs in Aozumi?

Open the app's Deployments tab and select a release to read its build output and runtime logs. Agents can read the same logs, redacted and size-bounded, with the MCP logs tool.

Why does my deploy fail with a health check error?

The app did not answer in time on the port Aozumi expects. Make sure the server listens on the PORT environment variable rather than a fixed port, starts quickly, and returns a 2xx response from its health endpoint.