> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/troubleshooting/i-cant-publish-my-pages.md). # Can't Publish Pages ## I can't publish my Pages ## If you see no builds: If this happens, you can force a rebuild by clicking the Rebuild button​. Once the page has been rebuilt, you will then be able to rebuild.
If you need to rebuild multiple pages, you can do that by going to Operations > Mass Build & Publish > Mass-Build. Please​ note that it will take a couple of minutes to rebuild before you can publish. ## If a build stays in "Starting" **Starting** is the status Limio gives a build before the build service reports its own status. Limio asks the build service for the true status only after five minutes. A build that shows **Starting** for the first few minutes is therefore normal, and a busy queue can hold it there for longer. Wait five minutes, then refresh the build list. The status changes to **Building**, or to the status that the build service gives, which includes **Failed**. If the build stays in **Starting** for more than 15 minutes: 1. Click **Rebuild** on the page. A new build replaces the one that did not report. 2. If the new build also stays in **Starting**, or the build fails, look at the custom components on the page. A page build stops when a custom component in it does not build, so a component that a developer changed recently is the first thing to check. Build that component on its own to see the error. 3. If the page has no custom components, or the component builds correctly on its own, raise a support request. Give the page path and the build ID from the build list, because Limio Support needs the build ID to find the build log. --- # 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.limio.com/support/troubleshooting/i-cant-publish-my-pages.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.