Help Centre

Account, billing & data

Offline use and the installed app

Understand VoltMate's PWA/offline shell and why failed offline writes, AI requests and server actions are not silently queued for replay.

offlinepwainstalled appinstallservice workerreload

Before you begin

  • A supported modern browser. Install availability depends on the browser/device PWA capability.

What offline support means

VoltMate can provide an installed-app experience and selected cached static resources. It is deliberately not designed to cache private authenticated API responses or queue failed business-data writes for automatic later replay.

When the connection drops

  1. 1

    Read the offline banner before continuing work.

  2. 2

    Treat live data, saves, AI analysis and other server-backed actions as unavailable while offline.

  3. 3

    Do not assume a failed action is queued or saved.

  4. 4

    When the connection returns, use Reload current data when VoltMate asks for a fresh reload.

  5. 5

    Re-check the record from the server before re-entering or submitting work, so you do not create duplicates or overwrite newer information.

Safety and freshness

Information already visible on screen can be stale while offline. Do not rely on an offline screen as proof of the current certificate, job, payment, regulatory or safety state.

Common mistakes

  • Assuming a failed offline save or AI request will automatically replay after connectivity returns.
  • Re-entering the same record immediately after reconnecting without first reloading current server data.
  • Relying on an offline certificate, payment or regulatory screen as proof of the current server state.

Troubleshooting

If the installed app behaves unexpectedly after a release, reconnect and reload the current site data first. Browser/site-data controls can remove service-worker caches, but clearing site data can also remove local interface state.

Related guides