Sync and Collaboration
Why is a project not syncing?
Symptoms
- Changes made on one device do not appear on another.
- Surfaces or attachments are missing on a second device.
Likely causes
- Synchronisation currently covers survey points. Surfaces, alignments, features and attachments do not yet synchronise — that work is in development.
- The device is in Local Mode and is not connected to a server at all.
- The device is offline, and queued work has not yet been sent.
- The project is undergoing a one-time migration, during which synchronisation is deliberately refused.
Step-by-step checks
- Confirm which record type is missing — if it is not survey points, it is expected to be absent today.
- Confirm the device is signed in and connected to a server.
- Confirm network connectivity, and allow queued work to send.
Recommended solution
For record types that do not yet synchronise, move the project between devices as a project package. Note that importing a package always creates a new project — it never merges into an existing one.
- Applies to
- Current ARKAK versions. Broader entity synchronisation is in development.
If this does not resolve it
If the answer is not here, write to us. Include your device model, the ARKAK version, and what you were doing when it happened.