Check status, logs and a failed deployment
Find the failed step before changing the application.
Open the deployment detail page and identify the current state:
- building — dependencies or the build command are still running;
- deploying — the container is starting and health checks are running;
- queued — capacity is temporarily unavailable and QuikDB will retry;
- failed — the build, start command or health check did not complete; or
- live — the application is serving traffic.
For a failed deployment, check these items in order:
- the first error in the build or runtime log;
- the detected runtime and build command;
- the start command and required files;
- whether the application listens on the injected
PORT; - required environment variables; and
- repository and branch access.
After correcting the problem, redeploy. If it still fails, include the deployment ID and the first relevant error line when contacting support. Never email passwords, private keys or access tokens.