> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/issues-and-troubleshooting/known-issues-and-workarounds.md). # Known Issues & Workarounds Check current known issues and the temporary workarounds that keep you moving. Use this section when something works differently than expected and a workaround is already available. This section lists only active issues with a known workaround. If we know a temporary way to keep working, we post that workaround here. When the issue is resolved in a product update, we mark it as resolved. After that, we remove the workaround from this page. ### How to use this section Start with the area where the issue appears. Check whether the issue matches the symptom you see. Follow the workaround until a product update resolves the issue. ### What each issue includes Each issue explains: * what goes wrong * who or what is affected * how to keep working until the fix is released {% hint style="info" %} Some issues depend on your package, permissions, enabled features, or release timing. {% endhint %} ### Current issues by area If no issues are listed below, there are currently no published known issues with a confirmed workaround. #### BackOffice No published BackOffice issues yet. #### Mobile app No published mobile app issues yet. #### Integrations No published integration issues yet. #### Marketplace and Power-Ups No published Marketplace or Power-Up issues yet. ### Need more help? If a published workaround does not solve the issue, contact support. Include the exact error message, the affected area, and the steps you already tried. --- # 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://knowledge.out-smart.com/issues-and-troubleshooting/known-issues-and-workarounds.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.