> 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/scout-guide/no-connection.md).

# No connection

Event Wi-Fi is often bad. RAIDScout is built for that.

## Saving with no signal

When you save a match with no connection, the entry is **Kept on this phone**. It sends by itself as soon as the connection is back, from any screen, or the next time you open the app. You don't have to stay on the form.

## Waiting to send

While anything is still on the phone, **Waiting to send** shows at the top of **Scout › Matches** with each entry. Tap **Send now** to try straight away.

* **Still no connection:** they'll send by themselves once there is.
* **The server turned these down:** an entry the server refused, for example a match you don't have a seat in. It won't be resent. Read the message, then fix it or **Discard** it. Discarding an entry that never reached the server deletes it for good.

## Things to know

* Saving again is safe. The server keeps one entry per scout per robot per match, so a resend only updates it.
* Install the app on your home screen so it opens with no connection at all. See [Install on your phone](https://docs.raidrobotics.org/raidscout/getting-started/install-on-your-phone.md).
* Pit and pre-scouting forms need a connection to save. If one fails, you'll see **Couldn't save. Check your connection and try again.**


---

# 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/scout-guide/no-connection.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.
