This article explains why your offline changes in the BriqSafe app might be replaced when syncing after reconnecting. It is intended for field workers who record work offline and want to understand how their data is handled when syncing with other devices or the web app.
NoteRequired role: Engineer
How Offline Changes Sync and When They Can Be Replaced
The BriqSafe app queues your changes while you are offline and uploads them automatically when you reconnect to the network. However, some types of offline edits can be replaced or discarded during this sync process, depending on whether the same record was changed elsewhere in the meantime.
When the Sync-Conflict Notice Appears
A sync-conflict notice will appear if any of the following happened on another device or the web app during your offline session:
- A risk assessment, recommendation, or attachment was modified elsewhere; in this case, your queued change is dropped, replaced by the newer version from the other device.
- The visit was signed off on another device or the web app; then your queued sign-off is not applied.
The app does not merge changes. The version saved elsewhere takes priority, and your offline queued change is discarded and never retried.
Important: The Notice’s Blind Spot for Job Answers
The sync-conflict notice does not cover job answers (form responses to jobs). If the same job was completed or updated in the web app while you were offline, your queued job answers overwrite those changes silently when syncing. No warning or notice shows for this situation.
This means edits made remotely to the same job can be overwritten without any indication at sync. To verify what was actually recorded, you must re-open the job after syncing.
Checking Your Offline Changes and Sync Status
After regaining connectivity, check which changes are waiting to upload and confirm that your offline work has been successfully synced:
- Tap the sync indicator in the header (status button or dynamic island pill) to open the sync-status sheet.
- Review the summary card and the list of pending changes. Jobs are grouped by Location, other items appear under Other changes.
- Let the app sync automatically or tap the boost control on a change to upload it first.
- After syncing, use Get latest data to pull a fresh copy of the records.
Use this process to confirm what offline changes survived and to identify any sync conflicts or dropped changes.
Verifying What Was Recorded and Avoiding Concurrent Editing
Once syncing finishes, always re-open the affected record (visit, job, or risk assessment) to check exactly what data was recorded. If your offline change was dropped due to a sync conflict but is still important, redo it immediately.
Avoid editing the same risk assessment on both the web app and mobile app at the same time. Concurrent edits increase the chance of conflicts and lost data.
Summary of Key Points
| Conflict Type | Effect on Offline Change | Sync Notice | Action Required |
|---|---|---|---|
| Risk assessment, recommendation, or attachment changed elsewhere | Your queued change is dropped and replaced by newer version | Sync-conflict notice appears | Re-open record after sync to verify and redo if needed |
| Visit signed off on another device or web | Your queued sign-off is not applied | Sync-conflict notice appears | Re-open visit to verify sign-off status (cannot be applied twice) |
| Job answers changed on web during offline session | Your offline job answers overwrite the web changes silently | No sync notice appears | Re-open job after sync to confirm data; redo if necessary |