Offline & Sync Deep Dive
Technical guide to Opscel's offline-first architecture, sync queue mechanisms, conflict resolution, and troubleshooting sync issues in the field PWA.
Last updated: 21 May 2026
30-Second Version: Opscel's field PWA is offline-first — engineers can capture photos, fill forms, sign off jobs, and log defects without internet. All writes queue locally in IndexedDB and sync automatically when the browser detects you're back online. Concurrent edits to the same queued item merge into one write rather than one overwriting the other. This guide covers technical architecture, sync indicators, cache management, and troubleshooting for engineers and admins dealing with sync issues.
Who Needs This Guide
- •Field Engineers: Understand what works offline and how to troubleshoot sync problems on-site
- •Office Managers: Diagnose sync issues reported by engineers, monitor sync health
- •Admins: Configure offline settings, manage cache quotas, understand sync architecture
Key Offline Benefits
- •No data loss: all work queues locally and syncs when online
- •Consistent UX: app works identically online and offline
- •Automatic retry: a failed sync retries immediately, up to 3 attempts total, no backoff delay
- •Merge, not overwrite: two edits queued for the same item are folded into one write, not resolved by discarding either side
- •Visual feedback: sync indicators show queue status
Need More Help?
If you're stuck or need assistance, our support team is here to help.