HEALTHCHECK_FAILED
What it means. The new version started but did not answer a request.
What to do. Make sure the server listens on process.env.PORT and responds to GET / within 10 seconds. Open log_url for the startup output, then re-run deploy. The previous version is still live.
- HTTP status: 422
- Retryable after applying the fix: yes
Every failure from the CLI or an MCP tool has this shape:
{
"ok": false,
"code": "HEALTHCHECK_FAILED",
"message": "The new version started but did not answer a request.",
"fix": "Make sure the server listens on process.env.PORT and responds to GET / within 10 seconds. Open log_url for the startup output, then re-run deploy. The previous version is still live.",
"file": "<where to edit, when known>",
"retryable": true,
"docs": "https://docs.uarpie.app/errors/HEALTHCHECK_FAILED"
}
Apply fix (edit file when it is given), then run the same command again.