Error codes

When a failed deploy matches a known cause, Gheima ends the deploy log with a code such as [GH-OOM] and shows the same code on the deployment’s “What went wrong” panel. A code always means the same thing, so you can search for it or quote it in a support ticket.

GH-PLATFORM · This failed on our side, not in your app.#

Cause

The build ran into an internal platform error. Nothing in your repository or your settings caused it.

Fix

Retry the deploy. If it fails the same way again, open a support ticket and include this deployment — our team already has the details.

GH-OOM · The process ran out of memory and was killed.#

Cause

It was stopped with exit code 137 — the container hit its memory limit, not a crash in your code.

Fix

Raise the memory in Settings → Resources (up to your plan ceiling). If the build itself is what runs out, cut what it loads at once — fewer parallel workers, a smaller bundle step.

GH-REPO-SIZE · The repository is too large to build.#

Cause

The checkout exceeded the build disk limit before the build started. This is usually committed build output, vendored dependencies, or large binaries in git history.

Fix

Add build output and dependency directories to .gitignore, move large assets to object storage, and set a root directory in Settings → Build & runtime if only a subfolder needs building.

GH-NO-START · Nothing tells the platform how to start your app.#

Cause

The image built, but no start command was detected — there is no start script in your manifest and none is configured on the service.

Fix

Set a start command in Settings → Build & runtime (e.g. `node dist/server.js`), or add a `start` script to your package.json. Make sure it listens on the port configured for this service.

GH-NPM-ERESOLVE · Your dependencies conflict and npm refused to install them.#

Cause

npm hit an ERESOLVE peer-dependency conflict: two packages ask for incompatible versions of the same dependency.

Fix

Reproduce it locally with a clean `npm install` (delete node_modules and package-lock.json first), fix the version conflict it reports, and commit the updated lockfile. Do not paper over it with --force.

GH-PRERENDER-ENV · Your framework ran your code during the build, with no environment.#

Cause

The build failed while pre-rendering pages. Runtime environment variables are not available during the build unless you expose them, so anything reading a database or an API at build time gets nothing.

Fix

Open Environment → Build-time variables and expose only the keys the build needs (the panel suggests them). Alternatively, move that data fetching to request time so it runs with the full runtime environment.