Account and Settings
Session Sync settings and saved changes
Read local Guide session status, retry details, and the conditions for automatic synchronization.
Settings > Mobile & Offline > Session Sync shows recoverable Guide session changes recorded for your account on this device. Use the same account and device where the work happened. Another browser profile or device has its own local records.
Read the summary and details
- Open Session Sync.
- Review Sessions, Changes, Retry, and Blocked. Blocked includes sessions with a conflict; Changes counts saved operations, not answered questions.
- Find the Guide row and select Details.
- Read Recorded sync state, Saved changes, recorded attempt counts, last attempt time, and whether each change is eligible for automatic replay.
- Select Close to return. Use Refresh sync status to reload the saved device state after returning to CareMap or reconnecting.
Each row includes a Guide reference and device session reference, so similarly named sessions can be distinguished. Saved guide session can appear when its name is absent from the current workspace view. That alone does not mean the Guide was deleted or your access was removed.
Details show safe diagnostic categories without displaying answer contents or raw errors. Some older entries have no per-change metadata or recorded attempt time; the summary cannot establish their underlying cause.
| Status | Meaning |
|---|---|
| Queued | Saved changes are waiting for connection and session conditions that allow replay. |
| Syncing | The device last recorded an attempt in progress; server acceptance is not yet confirmed. |
| Retry | An attempt did not complete or needs review. Check each change’s eligibility. |
| Blocked | Package or closed-session/report state prevents replay. |
| Conflict | Server state changed; automatic replay will not overwrite it. |
No pending sessions recorded means no waiting session changes are recorded here. It is not proof that a particular answer reached the server. Check the actual session or Report when confirming an outcome.
Let eligible changes sync
Keep CareMap signed in, online, and visible on the device with the saved work. Background checks run about every ten seconds and when you reconnect or return to the app. An open player manages its own session. A check is an opportunity to retry, not a promised completion time, and the app does not display an exact next-attempt time.
Refresh sync status only reads local state. It does not retry or clear changes. Details is also read-only; there is no conflict overwrite or discard control here.
If changes remain blocked, follow Recover offline Guide sessions. Preserve local data while investigating. Local recovery has limits and is not a permanent backup.