> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/troubleshooting.md). # Troubleshooting This is where you come when something in your integration isn't behaving the way you expect, or when you'd rather catch a problem before it happens than debug it in production. It brings together practical checklists for the milestones every partner integration passes through, explanations of the errors and edge cases you're most likely to run into, and the background you need to reason about failures instead of just reacting to them. If you're looking specifically for how authentication, requests, and error handling are built under the hood, that detail lives in [Technical Concepts](/partner/troubleshooting/technical-concepts.md), the subsection just below — start there when you need to understand the *why* behind an error, not just how to fix it. --- # 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.mdintegrations.com/partner/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.