Offline sync and field readiness

Offline-first behaviour

Field records can be created with device-side identifiers and queued until connectivity is available. Sync endpoints and services must treat retries as normal and deduplicate safely.

Before deployment

Test the exact device models and network conditions expected in the field. Verify assignment download, offline capture, restart persistence, queued records, partial connectivity, retry, and successful server acknowledgement.

When sync is slow

Check the pending record count, attachment sizes, device storage, network path, queue depth, Go sync service health when enabled, PostgreSQL pressure, and Redis/Horizon state. Avoid clearing app data while unsynced records remain on the device.