1. Home
  2. Docs
  3. Operations & troubleshooting
  4. Mobile sync incidents
Operations & troubleshooting

Mobile sync incidents

Respond to slow or failed field synchronisation without deleting unsynced data.

Supervisor v2026.10 Updated 4 Nov 2026

Determine the scope

Find out whether the problem affects one device, one network/geography, one app version, or most users. A widespread issue points to central infrastructure or a release problem.

Device checks

Record app version, user, device identifier, pending count, attachment size, last successful sync, storage, device time, and whether the same record repeatedly fails.

Server checks

Review sync API latency, Go sync service health when enabled, Redis/Horizon backlog, PostgreSQL CPU/locks, network errors, and request-size limits.

Protect local data

Do not uninstall the app, clear storage, or reset a device with pending unsynced records unless a controlled recovery has already copied or safely transferred those records.

Was this page helpful?

Still stuck?

Open a ticket and reference this page — we will pick it up from there.

Open a ticket