> For the complete documentation index, see [llms.txt](https://docs.limescripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limescripts.com/help-center/troubleshooting.md). # Troubleshooting ## Login or checkout does not continue Check your connection and try the login again. Confirm that necessary browser storage is available. The account dropdown lets you disconnect the store's basket connection and retry with the right account. A completed payment should be checked against its receipt before starting another purchase. ## Purchase is not visible Check that payment completed and that you are using the same Cfx.re account on the Portal as during checkout. Contact support privately with your transaction reference if it is still missing. ## Resource fails to start Check the first relevant server-console error, the installed folder structure, required dependencies and start order. For an entitlement error, check that the server license key belongs to the account that owns the resource. Preserve the original downloaded files. ## Database error Back up first. Confirm the configured database, connector and documented migration status. Do not repeatedly import SQL or delete tables to test a fix. ## Client interface or gameplay issue Check the client's F8 console and the server console. Reproduce with the documented configuration on a staging server. Note any conflicting resources or recent changes. If none of these checks resolves the issue, share redacted logs and reproduction steps in [Discord](https://discord.gg/p58kubnUx8). --- # 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://docs.limescripts.com/help-center/troubleshooting.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.