AI build error explanations
When a build fails, its logs can be long and difficult to scan. Deplomo can use AI to summarize the failure and suggest a next step. You can request an explanation from a failed build in the Deployments or Builds view. If the explanation is unavailable, use the full build log to investigate.
What the explanation uses
The explanation is based on the failed build’s log output. It can help you identify a failing build stage, a compiler or package-manager error, a runtime-version mismatch, or a configuration issue. It does not inspect or change your repository.
Open the failed build
In your service dashboard, open Deployments or Builds and select a build with failed status.
Request an explanation
Select Error explanation. Deplomo returns a short explanation and, when it can identify one, a suggested next step.
Check the suggestion
Compare it with your repository and service settings, including the lockfile, root directory, Dockerfile, build command and build-time variables. Treat it as a diagnostic aid and confirm the cause in the full log before changing your project.
Apply a fix and deploy again
Make the change in your code or settings, then start a new build or select Redeploy. Compare its result with the failed build.
The explanation uses a limited tail of the failed build log. Known secret patterns are redacted before the log is sent for analysis, but redaction cannot guarantee that every sensitive value is detected. Keep credentials and other secrets out of build output.
Common build errors
These examples can help you decide what to check in the logs. The explanation may suggest a next step when it can identify one.
| Error | Example in the log | What to check |
|---|---|---|
| Dependency conflict | ERESOLVE unable to resolve dependency tree | Check package versions and peer-dependency requirements. |
| Missing build package | fatal error: Python.h: No such file or directory | Check whether the required system package or headers are available in the build environment. |
| Build runs out of memory | JavaScript heap out of memory | Check memory use and the build’s resource needs. |
| Incorrect file path | Cannot find module '@/components/...' | Check the path and filename case; Linux paths are case-sensitive. |
| Port configuration | Application failed to respond on PORT | Check that the application reads PORT and listens on 0.0.0.0. |
Examples of what to investigate
TypeScript or framework version conflicts
If a framework build stops on type errors, use the log to identify the first relevant compiler message. Check the referenced file and line, along with the versions of the framework, compiler and related packages.
Variables needed during the build
Some front-end frameworks need environment variables while building. A variable set only for runtime is unavailable during that stage. Check the build log for the missing variable and add it as a build-time variable if the application requires it.
AI explanations and manual log review
An AI explanation can help you focus on the relevant part of a long log. The full log remains the source for checking the exact error and deciding what to change. Confirm suggested commands or dependency changes against your project and the package’s documentation.
Build errors and runtime errors
The AI explanation is for failed builds. It does not diagnose runtime crashes.
If a build succeeds but the application crashes after starting, review Runtime Logs and check the process status, listening port, environment variables, add-on connections and memory use. See the troubleshooting guide for more help.