Using Offline Mode

Using Offline Mode

Venue Wi-Fi drops, tunnels, dead zones — the app keeps taking the actions that matter most and syncs them when you're back. When you lose signal, an offline banner appears across the Dashboard.

What Keeps Working

Ticket scans, RSVP and reservation check-ins, direct ticket sales, and accepting or declining provider booking requests all queue locally instead of failing.

Each queued action gets a short local reference so you can identify it before it syncs. A queued action is not verified yet — the server hasn't seen it, and it can still be rejected when it arrives. If that happens, the offline queue tells you why.

Your Tickets Without Signal

The app keeps a copy of your upcoming tickets and their QR codes on your phone. It's refreshed when you sign in, whenever you open the app, and in the background every few hours while you have a connection — so at a door with no signal, open My Tickets and show the ticket's QR as usual. Transferring a ticket still needs a connection, and the copy is wiped from the phone when you sign out.

The Offline Queue

The queue widget on the Dashboard lists everything waiting, and the full Offline Queue screen breaks it down per action with its status: pending, retrying, failed, or conflict (the server's copy disagrees with yours and needs a decision).

From there you can retry a failed action, remove one you don't want, and resolve a conflict. A conflict usually means the same ticket or booking was changed on another device while you were offline.

When It Syncs

The queue syncs automatically as soon as your connection comes back — you don't have to pull to refresh or reopen anything. Scans made while offline are also cached locally to stop the same ticket being accepted twice.

An action that's been waiting a long time is not dropped: it stays queued until the server is genuinely reachable, rather than being given up on after a few failed attempts.