Data management
Offline & sync
What still works without a connection, and how the sync indicator reads.
Current connection requirements
Goji currently needs a working connection to save clinical changes reliably. If your connection drops while a session is open, the fields remain visible in that tab, but they are not durably stored on the device and may be lost if you refresh, close the tab, or restart the browser before the save succeeds.
Warning
The existing sync foundation
Goji contains a local queue, retry loop, and sidebar status indicator intended for offline-capable writes. No current charting action is connected to that queue, so the indicator must not be treated as confirmation that a failed clinical save is safely waiting on the device.
What durable offline charting will require
The first target is deliberately narrow: an already-open session should store each accepted edit on the device before reporting success, survive a reload or restart, show whether it is local or synced, and reach the server after reconnecting without silently overwriting a newer version.
- Saved on this device will mean the local write is durable.
- Synced will appear only after the server accepts the change.
- Needs attention will surface a conflict or failed retry instead of hiding it.