Why is my build failing, and how do I fix it?

When a deployment fails, Forte tells you which step failed and why — start with the logs.

Read the build logs

Open the deployment in the console and read the build and deployment logs top to bottom. The failing step is called out, and the error just above the failure is almost always the real cause.

Common causes

• The build command failed. Your app doesn't build cleanly — a compile error, a missing dependency, or an out-of-date lockfile. Reproduce the build locally, fix it, and push again.
• A monorepo built the wrong app. Forte auto-detects your language and framework; for a monorepo, set the base directory so it builds the right package. See Monorepo Support.
• Nothing is listening on the expected port. Forte discovers your app's port for health checks — make sure your app binds to the port it's given and starts listening.
• A required environment variable is missing. Add it to the service — see How do I set environment variables and secrets?

Still stuck?

Once the app is running, every request is linked to the log lines it produced, so you can trace failures by request — see Monitoring. If the build itself won't pass, contact support with the deployment link and we'll read the logs with you.