When something in Sessio misbehaves
When something looks stuck, the useful checks are small, and they solve more of these moments than they sound like they should: which browser, whether you are online, and whether the form is waiting on a required field.
The timer
The timer may not start, may freeze, may disagree with the ambient display, or may show a duration you did not expect. If the duration looks wrong, check the session's duration and whether you edited the timer mid-session. Setting a new remaining time is supposed to change the countdown, and it leaves the timer paused until you resume. That pause can look like a freeze if you are expecting it to run on its own.
If a refresh does not help, try another supported browser on a stable connection. If it is still wrong, write support with the steps you took and the approximate session time. Those two details make it much easier to see what happened.
The ambient display
The client screen may sit on idle, miss pause and resume, or show a different timer than your dashboard. None of that means the session itself is lost. It usually means the two screens have stopped hearing each other.
On the same computer, both windows need the same browser and the same Sessio site. A dashboard in Chrome and an ambient window in Safari often will not stay in step. Close the ambient window, open it again, and test pause and resume.
Across devices, both need to be online. Scan the tablet QR code again from the dashboard. If the iPad timer still looks old, refresh Safari and confirm the session is still running.
On the iPad, set Auto-Lock to a long duration or to Never while it is plugged in. Add the ambient page to the Home Screen so it opens with less browser chrome. Guided Access keeps the iPad on that screen if a client might tap it.
Browsers
Current Chrome, Safari, Firefox, and Edge are the desktop browsers to use. On a phone, Safari on iOS and Chrome on Android are the supported ones. iPad Safari is the one to use for the client display. Internet Explorer and the old Edge are not supported. Keep the browser updated, and leave JavaScript and cookies on. Strict Safari privacy settings sometimes need a looser cookie setting before things save or sync. If saves keep vanishing in Safari, that setting is the first place to look.
Saves that do not stick
If a change disappears after reload, or Save looks dead, check the connection first, then the form. Some fields have to be filled before save works: both names on a client, a password of at least eight characters, a confirmation that matches. Fix the hint on the form, then try again. The form is usually telling you what it still needs.
If it still fails, contact support with the page name, what you tried to save, about when it happened, and any error text on the screen. A screenshot of that text helps more than a general "it would not save."