How Offline Data Is Merged Back

The Sync Process

When your device reconnects, InspectERM automatically begins uploading all data that was created or modified while offline. This is called the sync flush.

Step-by-Step Sync Sequence

1. Connectivity detected - The network monitor fires an event
2. Sync dot turns yellow - Upload begins
3. Queue flush starts - Items upload in this order:
   • Inspection item results
   • Work log entries
   • Photos (uploaded after their parent records are confirmed)
   • Status updates
4. CloudERM confirms receipt - Each item is marked as synced after server acknowledgment
5. Work list refreshes - The app fetches fresh data to show new assignments or changes
6. Sync dot turns green - All pending data confirmed synced

What Happens to Each Data Type

Data Type	Merge Behavior
Inspection item results	Applied to the inspection record in CloudERM - last write wins
Work log entries	Created as new records with the correct creation timestamp
Task status updates	Applied to the task; if the task was already updated elsewhere, server conflict rules apply
Photos	Uploaded and attached to the associated item or work log entry

Timestamps

Offline entries use the device's local timestamp at the time they were created - not the upload time. This ensures the CloudERM audit trail accurately reflects when work was actually performed.

If Upload Fails

If an item fails to upload (e.g., a server error):

• The item remains in the queue
• The next sync attempt will retry it
• The sync dot may stay yellow longer than usual
• If the issue persists, contact your CloudERM administrator

Concurrent Updates

If another user modifies the same task or inspection item while you were offline:

• Your offline data is uploaded regardless
• For fields where both users made changes, CloudERM applies conflict resolution - the most recent server-side write typically takes precedence
• This scenario is uncommon since items are generally assigned to one person at a time