Sync state (7) + pending items

Sync status is more than one dot — this page covers the full seven states, the pending-items list, and how to handle sync errors.

Seven sync states

State	Meaning
✅ Synced	Local matches cloud, nothing pending
🟡 Pending sync	Changes not yet pushed (pending)
🟡 Syncing	Currently pushing
❌ Sync error	Push failed (rate limit, server issue, etc.)
🔒 Sign-in needed	Session expired — re-sign-in to keep syncing
✈️ Local mode	Manually offline, or no network detected
⚠️ Conflict	The same file was edited on multiple devices — needs resolving

The pending-items count

When changes haven't synced yet, the indicator shows how many are still waiting:

3 pending

Seeing that something is still pending lets you decide whether to wait before switching devices — let the count drop to zero first.

Last sync time

Next to the indicator, the last sync time is shown:

• "Just synced" / "3 minutes ago" — normal
• "Over an hour ago" — a warning sign; something pending may have failed to push, consider a manual sync

Triggering a manual sync

Don't want to wait for background sync:

• Click the sync icon → force-push all pending changes

Handling sync errors

A failed push shows the generic Sync Error state. There's no per-reason breakdown — but you rarely need one, because Slima keeps retrying in the background:

• Transient failures (request spikes, a brief server hiccup) — leave it; sync auto-retries and the state clears on its own.
• Session expired — if your session has lapsed, the state switches to Sign-in needed; sign in again and syncing resumes.
• Conflict — the same file was edited on two devices; this is its own ⚠️ state, resolved in the conflict resolution flow.

Related

• Connection modes
• Offline writing
• Sync status indicator (the dot-color view)