PoolHelm is slow, stuck, or won't finish loading

Try these first, in order. Between them they fix the large majority of cases:

1. Reload the page. Genuinely — a stalled request doesn’t recover on its own, and a reload starts it again.
2. Check your connection. A weak or flapping connection is worse for PoolHelm than no connection at all: with no signal it works offline and tells you so, but a connection that keeps half-dropping can leave a request hanging for half a minute or more before it gives up.
3. Switch networks. Off the site Wi-Fi and onto cell data, or the other way round.
4. Try a different device, if you have one to hand. It tells you whether the problem is your machine or your account.

A known one, stated plainly: on a flaky connection some requests can hang for 30 to 45 seconds before failing rather than giving up quickly and retrying. That’s a fault in PoolHelm rather than in your internet, it’s known, and a fix is on the list. A reload is the workaround.

If a technician is stuck mid-visit, they should not start the visit over. Everything after Start Service works offline and syncs when the signal comes back. Re-recording a visit makes it harder to untangle, not easier.

If it’s happening constantly, on more than one device, email support@poolhelm.com with what you were doing and roughly when. That’s enough to find it in the logs.