> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidscout/admin-guide/event-day-troubleshooting.md).

# Event-day troubleshooting

| Problem                                             | What to check                                                                                                                                                           |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No schedule, or it's out of date                    | **Manage › Events**: is the right event **Active**? Tap **Sync now**. Early on, the schedule may only exist in Nexus; The Blue Alliance takes over once it has one.     |
| Scores or rankings aren't updating                  | **Sync now** in **Manage › Events**. Check **Some data sources aren't set up**, and the keys in **Manage › API keys**.                                                  |
| Someone sees "Your account doesn't have a role yet" | Give them a role in **Manage › Users**.                                                                                                                                 |
| A scout can't save their match                      | Read the message on screen. A scout can only save the robot their seat is on (or one handed to them to rescout). Check their seat in **Manage › Schedule**.             |
| A scout's saves aren't showing                      | Their phone may have no signal. **Waiting to send** on **Scout › Matches** lists entries still on the phone; **Send now** retries.                                      |
| A scout lost their seat                             | Check **Manage › Schedule** and change the seat.                                                                                                                        |
| Numbers look wrong                                  | Work through **Data › Audit** and send robots to rescout. See [The Audit and rescouts](https://docs.raidrobotics.org/raidscout/scout-lead-guide/audit-and-rescouts.md). |
| Slack pings aren't arriving                         | **Send test** in **Manage › Slack**. Shift pings need a live match number, from Nexus or the last scored match. Check the person's **Slack member ID**.                 |
| Robot photos don't show on the pit form             | R2 isn't set up. See [Robot photos](https://docs.raidrobotics.org/raidscout/admin-guide/robot-photos.md).                                                               |
| The app looks out of date                           | Close and reopen it, or reload. Check the version at the bottom of the sidebar.                                                                                         |

When you report a bug, click the version at the bottom of the sidebar to copy it, and paste it into your message.


---

# 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.raidrobotics.org/raidscout/admin-guide/event-day-troubleshooting.md?ask=<question>&goal=<user_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.
