Skip to content
v2Latest
Feedback

Fix failed deployments

Read the build log, find the failing step and fix the most common errors.

On this page

When a deployment fails, the build log tells you which step stopped. Open the deployment and click View logs.

Common errors#

Module not found#

A dependency is missing from package.json or only installed locally. Run a clean install and commit the lockfile.

Shell
rm -rf node_modules
npm ci
npm run build

Out of memory#

Large builds can exceed the default 4 GB. Raise the limit under Settings → Build → Memory on Pro plans and above.

Build timed out#

Builds stop after 45 minutes. Turn on the build cache and avoid downloading large files during the build.

Redeploy#

After fixing the problem, push a new commit or click Redeploy on the failed deployment.

Note

Still stuck? Contact support with the deployment URL — we can read the full log on our side.

Was this article helpful?

89% found this helpful