Offline saves and device drafts
Synalux does not run entirely offline. Some saves are held on your device and sent later, some need a live connection, and a few things on your device are removed when you sign out. This page separates them.
What you see when the connection drops
- A panel above the page content appears when the browser is offline or when saved changes are waiting. Its title is Offline — changes stay on this device while you are offline. It shows Awaiting sync or review (this account), Filed copies (this account) and Device storage slots used (all accounts) as a count out of 200.
- Pages that loaded earlier can show a saved copy of their records, with Offline — showing a saved copy, Saved on this device: and the date, and This copy may be out of date. Reconnect and retry to check for changes. Patients, Assessments and Adult FBA / BIP are examples. When no complete saved copy exists, the page says Records are unavailable. and that this does not mean there are no records.
- Saved copies are encrypted on the device and are removed when you sign out.
Saves that wait on your device
When the browser is offline, editors that do not require a live connection keep your save on the device, encrypted, and send it when the connection returns. In the code, these include:
- adding or editing a patient;
- adding a program or goal from the patient list;
- creating, completing or deleting a task on the Tasks page;
- creating or editing a note on the Session Notes list.
Each saved change waits in a queue on the device. The queue holds 200 changes. When it is full, the page says Offline queue full (200 items) — connect to sync before continuing.
The Session Notes review actions (Submit for Review, Approve, Return note, Co-Sign, Finalize & Lock) need a connection. Offline they are not queued: the page says Reconnect before saving or reviewing this clinical record. Your unsaved changes remain in the editor. An offline note save that is queued says Saved on this device. It will be sent when you are back online; check Saved changes if it is not.
Saves that need a connection
These saves are refused while the browser is offline. The message is Reconnect before saving or reviewing this clinical record. Your unsaved changes remain in the editor. Keep the page open, reconnect, and save again. The saves are:
- assessment documents and assessment content versions;
- Adult FBA / BIP drafts, reviews and acknowledgements;
- progress reports;
- the patient chart's Tasks tab;
- copying a goal from the library, and acknowledging or resolving generated goal-target tasks;
- group sessions;
- Complete and save session, and Save draft in the session note editor.
Deciding what to do with a saved change from the Review saved changes list also needs a connection. Its comparison cannot be opened while the browser is offline, and an open comparison closes when the browser goes offline. Reconnect and open it again.
An in-progress data-collection session keeps an encrypted copy on the device. The Sessions header shows Retaining…, then Saved on this device, or Recovery needs attention.
How saved changes are sent
- The page tries to send waiting changes when the browser comes back online and when you open the portal. Open tabs take turns, so two tabs do not send the same change at the same moment. A change whose reply was lost stays in the list and can be sent again.
- A change that fails stays in the list. After a short retry delay (up to 30 seconds), it is tried again the next time the browser comes back online or the portal opens; a reconnect within that delay does not retry it, and waiting alone does not either. Retry this change tries it at once. Automatic retries stop after 8 failed attempts (the change shows Repeated failures — retry paused), and stop for a change the server refused because the record had changed (Conflict — saved change retained). Use Retry saved changes to retry everything, or Retry this change on one item.
- Some saved changes cannot be tied to the account that is signed in now, including entries from another account or an older version of the app. They stay encrypted on the device and are not retried.
Review saved changes
When a change needs attention, open Review saved changes. Each entry shows what was saved, when, and its state. For a saved edit or deletion of a patient, an assessment or a treatment plan, select Compare saved change to open Saved change compared with current record, which shows Saved on this device next to Current record. Other saved changes (tasks, session notes, new records) have no comparison; they can be retried. The comparison is read-only. Depending on the record, you can then:
- for a saved patient edit, choose the fields to apply or the fields to keep as they are now, and give a reason. Select File acknowledged copy once every saved field has a decision. The encrypted copy moves to Filed saved copies, stops being retried, and still counts toward device storage;
- for an assessment or Adult FBA / BIP change that conflicts with a reviewed record, select the saved sections to carry into a separate amendment, give a reason, and select Create amendment draft. The reviewed original is unchanged.
Session timing
Starting, pausing, resuming and completing a session that you opened from a scheduled appointment records the time from your device's clock. Sessions started with Start an unscheduled session do not record these events.
- If you are offline, the timing event waits in the queue and the Sessions header shows how many are queued ((n) timing events queued). When the connection returns it is sent with its original time. Each event has its own identifier, so a retry does not create a second record.
- The server sets the appointment's actual start and end from these times, and works out the duration as end minus start. It stores your device's time and its own receipt time. For an event recorded while the browser was offline, it also stores the time it was synced.
- The server refuses a time more than 5 minutes ahead of its own clock, or more than 30 days old. It also refuses an end time that is not after the start, or is more than 24 hours after it.
- Pause and resume events are stored. They do not change the duration the server calculates.
- A session ends when you complete it. The end time is the device time when the save is confirmed, not the scheduled end.
Idle sign-out and dictation
- You are signed out after 15 minutes without a mouse click, key press, touch or wheel movement in any open portal tab of the same browser. Moving the mouse counts once it has been still for 2 seconds, and scrolling counts in the tab where you scroll. The clock is shared by all tabs.
- Words recognized by dictation also count as activity, but only within 30 minutes of your last click, key press, touch or wheel movement. Silence and noise tags do not count. After that window, the 15-minute timer applies even if the microphone is on.
Drafts and sign-out
When you select Sign out, or the idle timer signs you out, the portal protects unsaved drafts before it clears the device:
- Sign out first checks for saved clinical changes and other saved work still held on the device (including copies already filed, and saved form drafts). If any remain, it stops with Saved clinical changes remain on this device. Resolve or sync them before signing out so their encryption key is preserved.
- An open SOAP editor stops accepting typing and dictation, and saves its text on the device. If it cannot, you stay signed in with The note open in the editor could not be saved on this device, so you are still signed in and it is still open. Copy its text somewhere safe or free up browser storage, then sign out again.
- Local SOAP drafts are sent to the server's Saved draft recovery. Each request must be confirmed within 10 seconds before anything on the device is cleared. A single draft over about 1 MB cannot be sent.
- When every draft is confirmed, the encrypted drafts, the saved record copies and the device key are removed, and you are signed out.
The idle timer does not show the message in step 1. When saved work remains or a draft cannot be confirmed, it keeps you signed in and says Session timeout: your unsaved session data could not be automatically saved. Please check your connection and save any open notes before leaving.
Drafts can be sent to recovery only while the browser is online. When recovery cannot be reached, for example because you are offline, you stay signed in and the page says Your unsaved notes on this device could not be saved to recovery, so you are still signed in. Check your connection and sign out again.
Some drafts can never be sent. A dialog titled Some drafts cannot be saved to recovery counts them by reason:
- Saved by another account on this device;
- Too large to save to recovery;
- Refused by recovery: you no longer have access to its workspace or patient;
- Unsaved changes to a document or spreadsheet: stay signed in and open it to save them, if you can still edit it;
- Unsaved document or spreadsheet changes saved by another account on this device;
- Unsaved document or spreadsheet changes kept by an earlier version of the app, for an unknown account.
Unsaved changes to a Drive document or spreadsheet are kept on the device, encrypted, for the account that made them. They are never sent at sign-out, because a save replaces the file on the server. When that account opens the file again with edit access, a document's changes are merged into its current version and saved. A spreadsheet's changes are restored only if nobody saved the spreadsheet since; otherwise the editor says they were not restored, and they stay on the device until you discard them at sign-out. Changes kept by earlier versions of the app are not tied to an account, so they are never applied.
Nothing is deleted unless you choose Sign out & discard, which deletes those drafts from this device for good. Stay signed in is the default choice, and Escape also keeps you signed in. A draft saved by another account is sent when that person signs in on this device and signs out.
The idle sign-out never discards. When some drafts cannot be sent, you stay signed in and the page says Session timeout: some drafts on this device cannot be saved to recovery, so you are still signed in. Sign out yourself to choose whether to keep them. When the open SOAP editor cannot save its text on the device, you stay signed in with The note open in the editor could not be saved on this device, so you are still signed in and it is still open. Copy its text somewhere safe or free up browser storage, then sign out again. When the drafts cannot be saved to recovery for any other reason, you stay signed in with Session timeout: your unsaved session data could not be automatically saved. Please check your connection and save any open notes before leaving.
Recovery copies are kept per account and workspace. On the SOAP page, Saved draft recovery lists only the copies you saved in the current workspace. See Clinical notes and documentation.