> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/bettor-sense/bettor-sense-user-interface/troubleshooting.md).
# Troubleshooting
"I can't access the UI"
* Confirm with your contact person that user accounts have been properly set up for your email.
* Verify you're using the correct credentials and access URL.
"I have logged in, but there isn't any data on the dashboard"
It's possible that happens due to more reasons, some most likely ones:
* Incorrect parameters stuck in local storage (cache).
* **Resolution:** Try clearing your local storage or checking if data is appearing in incognito mode.
* Your user account doesn't have permissions to view the data for the requested bookmaker.
* **Resolution:** Contact the person who helped you set up the account to review permissions.
"There seem to be missing risk scores for some players"
* Remember that risk scores are only updated for players who had betting activity the previous day.
* Risk scores are updated daily by 4 AM UTC - requests before this time may return previous day's data.
* In case you still feel like there is a risk score update missing, please send a message to the support channel in Slack and we'll review it.
"How do I contact support?"
* You can try asking the Bettor Sense chatbot as it's able to provide help on a variety of topics.
* If your questions still aren't answered, try contacting the Regulatory Services team at Sportradar by sending a message to the Slack channel or directly to your contact person.
---
# 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.sportradar.com/bettor-sense/bettor-sense-user-interface/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.