// GETTING STARTED
Understand Deployment Status
What PENDING, BUILDING, ACTIVE, FAILED, and INACTIVE actually mean.
Each push or manual trigger creates a Deploy record with one of these statuses:
| Status | Meaning |
|---|---|
| PENDING | Queued, waiting for a build slot. |
| BUILDING | Cloning the repo, building the image, and starting the container. |
| ACTIVE | Passed its health check and is now the live version — the previous active deploy is stopped. |
| FAILED | Build or health check failed. errorMsg on the deploy has the top-line reason; the full log has everything. |
| INACTIVE | A previously active deploy that's since been replaced or manually stopped. |
Only one deploy per project is isActive: true at a time. A new deploy only takes over once it passes its health check (an HTTP request to the container on the configured port succeeding, or returning any status under 500) — if it never becomes healthy within the timeout, it's marked FAILED and the previous deploy keeps serving traffic. Nothing goes offline because of a bad build.