SkieWhat triggers an instant sync on a managed device?
Two events trigger an immediate Skie sync: the device getting its internet connection back, and the screen turning on when the last sync is out of date. In both cases the device does not wait for the next scheduled check-in. It fetches current rules and reports its state straight away.
Scheduled syncs are fine for a device that is on and connected all day. The awkward cases are the ones in between: a tablet that lost Wi-Fi in a bus, a phone left in a locker overnight, a device that was switched off for the holidays. For these, Skie reacts to the event instead of waiting for a timer.
The first trigger is connectivity. As soon as Android reports that a network is available again, the Skie background service syncs. The second is the screen. When the screen turns on and the device has not synced recently, it syncs first. That is the moment a person is about to use it, so it is the moment the rules most need to be current.
Both triggers include retries. If the first attempt meets a weak connection, the device tries again rather than waiting a full interval. If the screen-on sync is late enough to cross the Due limit, the unlock gate described in the gate entry takes over and syncs before the user gets in.
What the admin sees: after a device returns from a long absence, its last-seen time on the dashboard jumps forward within moments of it being switched on and connected. If it does not, check Wi-Fi, battery and power, then use the breach centre to see how long it has been quiet.
Practical tip: when you hand out tablets after a break, ask staff to switch them on and connect them to Wi-Fi in one room. They will all catch up on their own without anyone touching a dashboard.