> ## Documentation Index
> Fetch the complete documentation index at: https://docs.time2.bike/llms.txt
> Use this file to discover all available pages before exploring further.

# Offline & sync

> How the operator screen survives flaky LTE.

Live Timing is **offline-first**. The operator screen records to your device first, then catches the server up in the background. If the network drops mid-race, nothing pauses.

## What you'll see

The top-right of the operator screen shows a sync pill:

* 🟢 **Synced** — everything is uploaded.
* 🟡 **N queued** — you have unsynced finishes waiting for the network.
* 🔴 **Offline — recording locally** — no network detected. Keep recording; queued events will upload as soon as you're back online.

## What survives what

| Scenario                              | Outcome                                                                                                                                                  |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| You refresh the tab                   | The screen rebuilds instantly from local storage. No data lost.                                                                                          |
| Wi-Fi drops mid-race                  | Recording continues. Queue grows; drains on reconnect.                                                                                                   |
| Phone dies, you swap to another phone | The new phone re-loads the session from the server. Anything that hadn't uploaded yet from the dead phone is gone — use the rescue export to recover it. |
| Server restart                        | No data loss; the server catches up from its own log.                                                                                                    |

## Rescue export

The footer of the operator screen has an **Export log** button. It saves a copy of everything your device has recorded so you can hand it to the race director if the device itself dies before it finishes uploading. The director can replay the file back into the session.

## When sync retries

The operator screen retries automatically:

* The moment network is restored.
* When you bring the tab back to the foreground.
* On a slow heartbeat while idle.

You rarely need to do anything; if you do, pulling-to-refresh kicks off a manual retry.

## Resume after long offline

When a device that's been offline for a long stretch comes back online, it reconnects and asks the server for anything it missed. The screen updates to match within a few seconds.