Documentation

Offline, Sync, and Conflicts

How local-first saving works, what pending states mean, and how to resolve blockers.

The technician app is built for local-first work. You can continue inspections offline, and data syncs when connectivity returns.

What is saved locally first

During inspection runtime, these actions are queued locally:

  • step submissions,
  • photo evidence uploads,
  • signature-related sync actions.

This prevents data loss during unstable connectivity.

Sync center essentials

Open More > Sync center to monitor:

  • connectivity status (online/offline),
  • active queue counts,
  • retryable/fatal failures,
  • direct links to conflict resolution.

Use Manual sync when you are back online.

Resolve blockers for one inspection

If a specific inspection is blocked:

  1. Open runtime and tap Resolve blockers (or open from Sync center).
  2. In conflict screen, run retry for blocked actions.
  3. If needed, use Refresh work data and retry again.

Protocol access requirement

Protocol pages are online-only. If you are offline, execution detail shows a reconnect message.

Practical troubleshooting order

  1. Confirm network is online in Sync center.
  2. Run manual sync.
  3. Open conflict screen for the affected inspection and retry.
  4. Refresh work bundle from inspection detail if runtime data is stale.
  5. Escalate to admin only after these steps fail.