Viewing build logs
Viewing build logs
Every deployment in Orbit has a complete build log. Use it to diagnose failed builds, check install output, or confirm your build command ran correctly.
Viewing the log for the latest deployment
On your project's Overview tab, the Latest build section at the bottom of the page shows the build log for your most recent deployment. If a build is currently running, the log streams live.
Viewing logs for a specific deployment
- Open your project in Orbit
- Click the Deployments tab
- Click any deployment in the list to open its detail page
- The full build log appears at the bottom of the detail page
You can also click View logs → on the Recent deployments list on the Overview tab.
Understanding the log
The build log shows the full output of your install and build commands in order:
[install] npm install
[install] added 847 packages in 4.2s ← cache hit, fast install
[build] npm run build
[build] > my-app@1.0.0 build
[build] > next build
[build] ✓ Compiled in 12.3s
[build] ✓ Linting and checking validity of types
[build] ✓ Collecting page data
[build] ✓ Generating static pages (24/24)
[deploy] Packaging artifact (2.4 MB)
[deploy] Deployment live
The Status card above the log shows whether the deployment succeeded, failed, or is in progress.
Build metadata
The detail page shows key facts about each deployment:
| Field | What it shows |
|---|---|
| Status | Current or final status (Live, Failed, etc.) |
| Branch | The git branch this deployment came from |
| Commit | The 7-character commit hash |
| Build time | Total time from queue to live |
| Cache | Whether a cache hit shortened install time |
Failed builds
When a build fails, the log shows exactly where it stopped and why. Common causes:
- Missing environment variable, your build command references a variable that isn't set. Add it on the Env vars tab and redeploy.
- Dependency install error, a package version conflict or a missing peer dependency. The
npm installoutput will show the error. - Build command error, a TypeScript error, linting failure, or test failure (if your build command runs tests). Fix the error in your repo and push.
- Out of memory, large builds can hit memory limits during compilation. Check your framework's memory settings or contact support.
Retrying a failed build
On the deployment detail page, click Retry to re-run the same commit. This is useful if the failure was caused by a transient network error during the install step.
Tip: The build log is truncated for very long outputs. If your log is cut off, the full output is still available, contact support and reference the deployment ID shown on the detail page.