> For the complete documentation index, see [llms.txt](https://eu.support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eu.support.backpack.exchange/report-issue-or-bug/exchange.md). # Exchange ### **How to report bugs or platform glitches on the Backpack Exchange:** If you encounter any irregularities or glitches, kindly follow this guide to share your observations. ### **1. Document the glitch (if possible)** * Taking a screenshot or a short screen recording can greatly expedite our troubleshooting process. * While this isn't mandatory, it provides our technical team with invaluable insights into the issue. ### **2. Send your report** * Forward your observations and any visual evidence to . * Provide comprehensive information: * Clearly describe the observed bug or glitch. Mention the device and browser you were using, steps leading up to the anomaly, and any other pertinent data. Remember, while visuals are beneficial, a detailed description is equally important. ### **3. Await our feedback** * Once you've relayed your observations, our team will commence its investigation. You may receive an acknowledgment or a tracking reference, assuring you that we're on the case.\ ‍ **Thank you for contributing to enhancing Backpack Exchange!** Your observations and feedback are crucial in ensuring our platform continues to operate at the highest level possible. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://eu.support.backpack.exchange/report-issue-or-bug/exchange.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.