SkieWhat happens to managed devices if the Skie server is down?
The devices keep enforcing the rules they already have. Policies are cached and signed on each device, so apps, schedules, filtering and hardening carry on as before. What pauses is change and reporting: new rules, fresh location and dashboard updates resume when the service is back and devices sync again.
A management service being unreachable should be an inconvenience, not an incident for the people using the devices. That is why Skie keeps enforcement on the device. Android applies the restrictions, the signed policy bundle sits in local storage, and neither needs a live link to run.
During an outage a device will try to sync and fail, then retry. It does not wipe its rules or fall back to an open state. The last-seen times on the dashboard will go stale, so you may see devices move through Due and Overdue because nothing has been heard, which is the dashboard being honest about what it knows rather than a sign of misuse.
The unlock gate is the part to understand. If a device passes the Due limit and someone unlocks it, the gate tries to sync first and only blocks if the sync cannot finish. During a long outage, that could gate devices that passed the limit. Offline mode, with its own allowed apps and maximum, is the planned way to cover long gaps at sites you know will lose connection.
Afterwards, devices catch up on their own. Each syncs when it next connects or the screen turns on stale, fetches current rules, reads protections back and reports. Nothing needs to be re-entered.
Practical tip: if your organisation has a critical day, such as exams, check the dashboard the day before and make sure every device was seen recently. Backups are taken nightly, and you can restore a previous version if a configuration was changed by mistake.