Scans not syncing after working offline
Klovio handhelds keep working when the network doesn’t. Every scan made offline is saved to a local queue on the device and sent to the server automatically once the connection returns. Nothing is lost — but sometimes the queue needs a nudge.
How the offline queue works
- Each scan is written to the device’s storage the moment you confirm it, whether or not there’s a signal.
- When the device reconnects, queued scans upload automatically in the background.
- Scans apply in the order you made them — a receive queued at 9:02 posts before a pick queued at 9:05, so quantities stay correct.
1. Check the queue depth
- Open the app menu on the handheld and look for the sync status indicator.
- It shows how many scans are waiting to upload. Zero means everything has synced.
- If the number is falling, the queue is draining — give it a minute before doing anything else.
2. Get the device reconnected
If the queue count isn’t moving:
- Walk out of the dead zone. Freezers, metal racking, and far corners of the building routinely block WiFi. Move toward an access point and watch the queue counter.
- Toggle WiFi off and on in the device’s Android settings. This forces the handheld to re-associate with the network, which clears most stuck connections.
- Confirm you’re on the right network. Zebra and Honeywell devices sometimes hop to a guest or IoT network with no route to the internet.
- Reboot the device if the queue still won’t drain. Queued scans survive a reboot — they’re stored on the device, not in memory.
Nothing is lost
Queued scans persist through reboots, app restarts, and even a dead battery. Don’t re-scan items just because the queue looks stuck — that’s how you end up with doubled quantities once everything syncs. Fix the connection instead.
When to escalate
Open a ticket if:
- The device is clearly online (other apps and pages load) but the queue count won’t drop
- The queue has been stuck for more than an hour after reconnecting
- Multiple devices on the same network are all stuck at once — that points at a network or firewall change on your side, and we can tell you what to check
Include the device model, the queue count, and roughly when the device went offline.
Still stuck? Create a ticket and we’ll help you drain the queue safely.
Didn't fix it?
Open a ticket and a real person from the WMSHero team will pick it up.