> For the complete documentation index, see [llms.txt](https://bluebricks.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluebricks.co/docs/help/troubleshooting.md). # Troubleshooting - [Authentication](https://bluebricks.co/docs/help/troubleshooting/authentication.md): Resolve login failures, expired tokens, API key issues, and collection access errors with the Bricks CLI and Bluebricks app - [Deployments & Runs](https://bluebricks.co/docs/help/troubleshooting/deployments.md): Resolve environment not found errors, slug conflicts, stuck runs, approval blocks, and lock issues during deployments - [Packages & Blueprints](https://bluebricks.co/docs/help/troubleshooting/packages.md): Resolve publishing errors, invalid bricks.json files, output reference issues, and other package and blueprint problems - [Cloud Connections](https://bluebricks.co/docs/help/troubleshooting/cloud-connections.md): Resolve cloud account connection issues for AWS, Azure, GCP, and self-hosted infrastructure - [Self-Hosted Runner](https://bluebricks.co/docs/help/troubleshooting/self-hosted-runner.md): Resolve common issues with the Bluebricks Deployments Controller (BDC) and Bricks Runner, including OOMKilled jobs, stuck tasks, and storage errors --- # 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://bluebricks.co/docs/help/troubleshooting.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.