> For the complete documentation index, see [llms.txt](https://docs.dappling.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappling.network/builds/troubleshoot-a-build.md). # Troubleshoot a Build ## Troubleshoot Build Failures If your build encounters an issue, dAppling will report the error message on the Deployments page, allowing you to investigate and address the underlying problem. ### Investigating Build logs Build logs offer insights into what occurred during the deployment build and can be accessed by following these steps: * From your dAppling dashboard, select the project, and then navigate to the Deployments tab. * Choose the specific deployment. When there are build issues, you will notice an error status next to the deployment name. On the deployment's page with an error status, you'll find a summary of the error in the preview section. In the Deployment Details section, expand the Building accordion to access the logs. Scroll through the build logs until you find a red section with the keyword "Error." This keyword may appear once or multiple times. In many cases, the last mention of "Error" may not provide the most indicative information. Look a few lines above to find additional error messages, which can help pinpoint the problem. Sometimes, errors may not be explicitly mentioned, but the output often contains clues about the issue's location. ### Preventing Build Issues It is advisable to build your project on your local machine first, using the build command specific to your project. This helps catch issues that are specific to your code or your project's dependencies. For instance, if you encounter an error from `npm run build` locally, you can address it before deploying on dAppling. ### Build Duration The total build duration is shown on the deployments page. Please note that a build can last a maximum of 25 minutes. If the build exceeds this time limit, the deployment will be canceled, and the error will be shown in the Deployment's Build logs. If you encounter this limit, reach out to our support. :cactus:*Fun Fact: A group of orchids is known as a "blue," while a group of cacti is known as a "forest."* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dappling.network/builds/troubleshoot-a-build.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.