Offline queue & syncing#

Agents work in basements, lifts and villages. The app is built for that: everything you do without a network is queued on the phone and uploaded automatically when a connection returns. Nothing is lost if the phone stays offline for a while.

Who this is for#

• Sales agents who noticed a "pending" indicator and want to know if their work is safe.
• Admins explaining sync behavior to the team.

Difficulty: Easy · Time: about 5 minutes · Prerequisites: none — this describes how the app behaves.

What queues, and what doesn't#

Queued items are stored in an on-device database and uploaded in order by the app's sync worker. Home shows a pending badge while items are waiting; you can watch the count go down after a good connection.

How the sync works#

1. Automatic, every ~15 minutes — a periodic background worker checks the call log and pushes any queued changes.
2. Automatic, on connection — queued work retries with exponential backoff; a flaky network just means later, not lost.
3. On demand — force it any time:
   • More → Device health → Background sync → SYNC NOW, or
   • More → Settings → Sync → SYNC NOW.
4. Failed items — if an item is rejected after retries, it stays visible in Settings → Sync, where RETRY FAILED re-sends it.

Step 1 — Check the queue state#

1. Open More → Device health and read the Background sync row:
   • "Last sync: 5 Oct, 9:41 am" — a successful upload has happened.
   • "Uploading now…" — the sync worker is running.
   • "Waiting for a connection" — queued, waiting for network.
   • "Some changes couldn't sync — we'll retry automatically." — backing off after a failure.
   • "No successful sync yet — waiting for the first upload." — first sync hasn't completed.
2. Tap SYNC NOW (Device health or Settings → Sync). The app also starts recording discovery at the same time.
3. Watch Home: the pending badge clears as items upload.

Step 2 — Work offline with confidence#

1. Take calls, write notes, change stages — the app applies them immediately on screen.
2. When the connection returns, the queue drains automatically; you do not need to keep the app open (the OS schedules the work).
3. If you are offline for a long stretch, connect to Wi-Fi and open the app once, then use SYNC NOW to drain faster.
4. For push-free periods, use Settings → Sync → SCAN CALL LOG NOW to pull recent calls immediately after reconnecting.

Expected result#

• Nothing you entered offline is missing after a sync.
• Device health's Background sync row shows a recent "Last sync" time.
• Home has no stale pending badge.

Common mistakes#

Troubleshooting#

• Pending badge won't clear — check connectivity and the Background sync row; tap SYNC NOW. If it reports backing off, wait a few minutes or retry.
• One item keeps failing — open Settings → Sync and use RETRY FAILED. If it still fails, note the item and contact your admin with a Device health support report (see below).
• Calls made yesterday appear only now — normal after long offline periods; the call-log scan uploads up to 500 rows per pass, so large backlogs drain across a few syncs.
• Correct in the app but not in the CRM on the web — the device may be pointing at a different server (check the server line on the login screen) or the item is still queued.

Technical details#

• On-device queue: Room database, drained by com.leadhub.sales.data.sync.SyncWorker (unique work leadhub_sync) using WorkManager constraints, exponential backoff and per-item idempotency keys — a retried upload cannot create duplicates.
• Call-log scan: CallLogSyncWorker (unique work leadhub_calllog_scan), periodic every 15 minutes, max 500 rows per scan.
• Server endpoints used: POST /api/v1/mobile/call-events, lead stage/notes/follow-up endpoints under /api/v1/mobile/leads/....
• The redacted support report from Device health (see Device health) includes sync state if you need to escalate.

Related guides#

• Calling from the CRM
• Device health
• Mobile not syncing / push not arriving
• Mobile troubleshooting