Offline

Offline Logging And Sync

What works offline today, how the browser queue behaves, and what users should do before and after reconnecting.

/tickets/create browser queue Mobile queued sync Reconnect and sync
Offline

Web Offline Flow

Log deliveries while offline on web

  1. Open /tickets/create while online at least once.
  2. If the connection drops, stay on that page.
  3. Save the entry and let the page store it in the browser offline queue.
  4. Reconnect to the internet.
  5. Leave the page open or click Sync Pending to push queued entries to the server.
  • The browser queue is device and browser specific.
  • If the user clears browser storage before syncing, queued entries can be lost.
Offline

Mobile Offline Flow

Log deliveries while offline on mobile

  1. Open the mobile app and sign in.
  2. Use New Entry.
  3. Save entries even if signal is unavailable.
  4. Reconnect and reopen the app so sync can finish.
  • Entries save locally first.
  • Photos can queue locally and upload later.
  • The app can build an offline pack for tides, dashboard data, and other cached sections.
Offline

Reconnect And Troubleshoot

What to do after signal returns

  • Reconnect the device.
  • Keep the app or delivery page open briefly so queued work can sync.
  • On the web delivery form, click Sync Pending if you want to force a retry.

What to check if sync looks stuck

  • Whether the user is actually online.
  • Whether the user is still signed in to the expected server.
  • Whether the page or app was reopened after reconnecting.
  • Whether the missing entries are still pending locally vs already on the server.

When to escalate

Move from user guidance to support if the same sync problem reproduces across devices, accounts, or repeated reconnect attempts.

Terms · Privacy · Help Center · Support