Logs and status

The app page shows whether your app is running, what it is printing, and the history of its deploys.

Runtime logs

Expand Runtime logs to see what the running container is printing right now. Refresh re-reads them; Copy copies the visible output.

If the app is not running you see App isn't running — deploy it to see its logs. Deploy it first.

Build logs

During a deploy, the Build log streams the build output. When it ends it reads Build succeeded or Build failed. Past runs are under History and Pipeline runs.

Status

The app's delivery status is one of Not deployed, Up to date, Changes pending, or Deploy failed. The lifecycle label (pending, live, stopped, and so on) is explained in apps, builds and deploys.

History

History has two tabs: Deployments and Builds, each filterable by status. Pipeline runs lists every deploy that ran, when, what triggered it (manual or push), and whether it succeeded.

Restart versus redeploy

• Restart (under Actions) runs the same image again. Use it to clear a stuck process. It does not rebuild.
• Deploy builds your current source into a new image and ships it. Use it after changing code.

What can go wrong

• "Couldn't load logs. Try refreshing." — A transient read error. Refresh.
• "App is not currently running" (on Stop) / "App is not currently stopped" (on Restart) — The action does not apply in the app's current state.
• "This app was stopped by an admin and can't be restarted. Contact support." — An administrator suspended it. Reach support.
• "This action isn't available right now — the app may be mid-deploy." — Wait for the running operation to finish, then retry.