> For the complete documentation index, see [llms.txt](https://docs.alkemi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alkemi.ai/documentation/basics/data-products/training-your-data-product/troubleshooting.md). # Troubleshooting ### Agent not understanding queries? * Check if you have training examples similar to the problematic query * Review your training data for accuracy * Add more diverse examples covering the missing use case ### Low certainty ratings on many queries? * Review the analysis provided for each low-certainty query * Look for patterns in what's causing low confidence * Consider adjusting your prompt writing style for clarity ### Automated generation producing poor results? * Switch to asynchronous generation for better quality * Review and edit generated examples * Provide more manual examples to guide the Alkemi Agent’s automatic generation --- # 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.alkemi.ai/documentation/basics/data-products/training-your-data-product/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.