DocsTroubleshooting
Fixing a failed deployment
The most common errors and how to solve them.
Troubleshooting 5 min read
When a deployment fails, your previous version keeps running. Open the failed deployment, read the last lines of its logs, and find the matching case below.
| You see | Likely cause | Fix |
|---|---|---|
Missing script: "start" | No start command defined. | Add a start script to package.json or set one in Settings. |
Health check timed out | App listens on a fixed port. | Listen on process.env.PORT. |
Cannot find module | Dependency missing from package.json. | Install it with npm install name and commit the lockfile. |
Out of memory | Plan too small or memory leak. | Check the Metrics tab, then upgrade or reduce usage. |
TokenInvalid | Wrong or missing secret. | Check the variable name and value in Environment. |
Crash loop detected | Process exits right after starting. | Run the start command locally to see the first error. |
Still stuck?
Open a ticket from the Support page and include the deployment ID. Our team can see the same logs you do and usually answers within a few hours.
Was this article helpful?