Working offline

Flows is built for job sites and vehicles where a connection isn't guaranteed.

What works without a connection

• Everything you've already loaded (workflows, active runs, recent records) stays visible, read from what was last synced.
• Checking a step, flagging it, adding a note, and commenting all work immediately — Flows never makes you wait for a network round-trip to see your own tap register.
• Guest mode (see Guest mode) is fully offline by construction — there's no server round-trip to wait on in the first place.

What's queued

While you're offline, your changes to an active run (checking steps, flags, notes, completing or cancelling it) are saved on the device and queued. The run's header shows QUEUED · n so you know exactly how many changes are waiting.

The moment your connection comes back — or Flows notices you've returned to the app in the foreground — the queue sends everything in the order you made it, so a step you checked before one you flagged stays in that order on the server too.

You're offline. Showing what was last synced. — this banner means you're looking at cached data; new information from teammates won't appear until you're back online, but your own changes are safe and queued.

If a queued change fails

On the rare case a queued change is rejected once you're back online (for example, a run was already completed from another device), Flows drops just that one change and tells you once — it won't retry it forever or block the rest of the queue.

What doesn't work offline

Creating a new workflow needs a connection (the editor's Save button is disabled with a note explaining why) — queued creation is a possible future improvement, not something Flows does today. AI assist, organizations, and anything involving another person (comments reaching them, notifications) obviously need a connection to actually reach anyone.