Sync, conflicts and working offline
What is on the phone, what has gone to the server, and what to do when two people changed the same thing or the server rejects a change.
- For
- Field crew
- Time
- 4 minutes to read
- Where
- Field app — Sync
- Updated
On this page
How sync works
- Everything you record is saved on the phone first, in an outbox. Nothing is lost offline.
- Sync runs by itself whenever the phone has a connection; Sync now forces it.
- Nothing is ever overwritten silently: if someone else changed the same thing first, you choose.
- 1 What needs you, and Sync now
- 2 A conflict: yours vs the server's
- 3 Keep mine · Take server's
- Read the status. 3 to sync (waiting on the phone), All synced, 2 need you (conflicts or rejections), Syncing…, Not synced. The last result says what was sent, received and uploaded.
- Resolve a conflict. The table shows each field that differs — yours and the server’s.
- Choose Keep mine or Take server’s.
Rejected by the server lists changes that broke a rule (for example, trees affected cannot exceed trees assessed). Correct the record and save it again, or dismiss the rejection.
Tips
- Sync before and after each field day. Before: the latest plots and targets. After: your work is safe on the server.
- On the web, a save that conflicts opens the same choice, field by field.
What it doesn’t do (yet)
- Conflicts are resolved record by record; there is no merge of two edits within one field.