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 back online. Last-write-wins conflict resolution ensures data consistency across devices. 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: failed syncs retry with exponential backoff
- •Conflict handling: last-write-wins prevents data corruption
- •Visual feedback: sync indicators show queue status
Need More Help?
If you're stuck or need assistance, our support team is here to help.