Offline and desktop states
A reference for everything VNCcontacts shows about offline, sync and the desktop app. The banner is hidden when you are online with nothing waiting.
Status banner
Section titled “Status banner”| Message | Meaning | What to do |
|---|---|---|
| Offline — showing saved data | No connection; you are reading a saved copy. | Keep working; edits queue. |
| Offline — N unsynced changes | Edits are queued on your device. | They send automatically on reconnect, or select Sync now. |
| N unsynced changes | Online, still draining the queue. | Usually clears itself; Sync now forces it. |
When the queue empties and you are online, the banner disappears.
Conflict banner
Section titled “Conflict banner”| Message | Meaning |
|---|---|
| A change to a contact was discarded because it had already been edited elsewhere. The latest version is shown. | Someone changed the same record first, so the newest server version wins and your stale edit is dropped. |
The banner names what was affected in plain words (a contact, a company, a tag, a list, a smart list, a custom field). Open the record to see the current values and re-apply anything you still need.
Storage-full banner
Section titled “Storage-full banner”| Message | Meaning |
|---|---|
| Your device is out of storage, so a change couldn’t be saved offline. | There was no room to store the change locally. |
Free up space, then re-apply the change.
Desktop app states
Section titled “Desktop app states”| Element | Meaning |
|---|---|
| Tray icon | The app is running; the menu has Open, Pause notifications and Quit. |
| Unread badge (Dock/taskbar) | Unread notifications, matching the bell. |
| Pause notifications | Do-not-disturb; toasts stop until you turn it back on. |
| Window close (macOS) | The app keeps running — select the Dock icon or tray to reopen. |
| Window close (Windows/Linux) | The app quits. |
How sync works
Section titled “How sync works”VNCcontacts shares the suite’s offline engine. Your edits are applied locally first (optimistic), sent in order when a connection is available, and the record is re-read afterwards so what you see is what the server holds. The engine is not gap-free: it re-fetches a whole list rather than an incremental delta, which is simple and always converges.