Cached view, not a live promise
When the portal says Offline snapshot or Cached view available, the screen is showing the last synced admin data. Users should expect some actions to wait until reconnect.
IgniteIQ offline mode is built for admin continuity. It keeps supported Company Admin pages available from the last synced snapshot, labels stale data clearly, and protects queued work with backend replay checks.
When the portal says Offline snapshot or Cached view available, the screen is showing the last synced admin data. Users should expect some actions to wait until reconnect.
Queued work is replayed through server checks. If the record changed while the user was offline, the portal can mark the item failed or conflicted instead of overwriting newer data.
Connection warnings include retry and dismiss controls. Failed queued work should tell the user which action failed and why it needs attention.
A page must be visited and synced online before the browser can reliably show it offline. First-time pages may still need internet because the route and its data are not cached yet.
Live writes, uploads, support tickets, course publishing, billing actions, and certificate changes may need reconnect or queue replay. The UI should say exactly what happened instead of showing a generic network error.
If a queued item conflicts with newer server data, the backend owns the safety decision. The user should see the failed action and the next step.
Sign in while online and open the Company Admin areas your team depends on.
Confirm the offline status badge shows the latest sync time before disconnecting.
Disable internet or use browser offline mode, then revisit the synced admin pages.
Check that cached pages load with offline snapshot language instead of a blank browser error.
Reconnect and confirm retry/sync messaging clears without losing the user’s current page.