Working offline and sync
How the Mac app keeps a local copy, syncs with your server, and handles changes the server refuses.
The Mac app works from a copy of your time on your Mac, so you can track time without a connection. This page explains how it syncs, what its status line means, and what happens to a change the server won't take.
How it works
- Changes are saved on your Mac first. Each one goes into your local copy and into a queue of changes waiting for the server, in one step.
- The app sends the queue to the server whenever it can, and pulls what changed on the server since the last time.
- A live connection tells it when to pull. When something changes on the server, such as a timer you started in the web app, the Mac app hears about it and pulls, usually within a second.
- It reconnects by itself, when the network comes back and when your Mac wakes. As a safety net, it also retries waiting changes every minute.
The local copy lives in ~/Library/Application Support/ChronoSlice/, in a folder for your server.
The sync status
The sync status is at the bottom of the sidebar and in the menu bar panel. It reads:
| Status | Meaning |
|---|---|
| Your organization's name | Nothing has synced yet in this session. |
Syncing… |
A sync is running. |
Acme · synced |
Up to date with the server. |
Acme · reconnecting |
Synced, but the live connection dropped. It's reconnecting. |
Offline · 3 waiting |
The server can't be reached, and 3 changes are waiting. They'll go when it's back. |
Sync failed |
The server answered with an error. Hover over the status for the reason. |
Signed out — sign in again |
The server stopped accepting this Mac's token. |
Acme · 2 refused |
The server refused 2 changes. See below. |
Sync Now in Settings, under Account, tries again straight away.
When two places change the same entry
If you change an entry on your Mac and someone changes it elsewhere, the app merges them:
- A field changed on only one side keeps that side's value.
- A field changed on both sides goes to the newer edit.
- A project and its task move together.
- A delete on either side wins over an edit.
Changes the server refuses
Sometimes the server won't take a change, for example because the entry has since been invoiced. The app never drops that silently. The entry stays in your list, marked Not saved on the server: with the reason, and a Revert button puts it back as the server has it. A message tells you when this happens.
What needs the server
- New tags need the server, so you can't make one while offline.
- Signing in needs the server.
- Stopping a timer when the server is read-only goes straight to the server. See When the server is read-only.
Signing out with changes waiting
If you sign out while changes are waiting, they're deleted with the local copy. The app warns you first and counts them. Reconnect and let them sync before you sign out. See Installing and signing in.
If it won't sync
See Troubleshooting.
Still stuck?
Send us a request: it goes to the people who build ChronoSlice, and the reply comes by email. Include your ChronoSlice version (Settings › Licence shows it) and what you tried.