Weak connection and no network

No offline mode

The terminal does not work offline: it does not queue operations, save locally, or send them when the network returns. Every scan requests the server. Without a connection, you cannot work; this is safer than picking half a cart “as if”.

Connection monitor

Every 5 seconds, the terminal sends a lightweight request and measures response time:

It takes two measurements to enter a bad state; recovery is immediate, so a brief network blip does not trigger an alarm. Hide the monitor with F6 → Connection monitor visible.

Step by step

Check the connection

1. Look at the lowest screen bar, below the counters. It shows a dot, state, and response time in ms.
2. Read Connecting…, Connected, Weak connection, or No connection. The dot is green, yellow, or red for the corresponding connected, weak, or no-connection state.
3. Tap the bar to open Connection diagnostics.
4. The window shows Current, Average, Min, and Max in milliseconds, then a chart of recent measurements.
5. At the bottom, Measurements: n · Lost: n · Last measurement: HH:MM:SS. A rising Lost count proves packet loss; show it to your supervisor or IT staff.
6. Close the window with the X in its header.
7. If the bottom bar is missing, press F6 and enable Connection monitor visible.

After unlocking the handheld or returning from another app, the bar briefly says Connecting…. This is normal: measurements pause while the kiosk is in the background and restart when you return.

The connection drops while saving

1. Do not repeat the operation blindly. First check whether it went through.
2. Replenishment shows a yellow Network error — state refreshed bar and The last operation was not confirmed. Check the counter on screen before retrying. Check the counter before deciding whether to retry.
3. Receiving says Press “Retry”. The retry uses the same identifier and will not post the goods twice. Press Retry; it is safe.
4. Packing when booking a courier says The courier did not respond in time. The parcel may have been shipped — check the parcels before trying again. Count parcels at the station before pressing anything.
5. In any other mode, refresh with F1 and compare the screen with what you are holding.

“Company settings missing” bar

1. A narrow bar appears above the bottom bar with a crossed-out Wi-Fi icon and Company settings missing — touch confirmation disabled until connected.
2. Do nothing; the terminal retries automatically at longer intervals, down to once every 30 seconds.
3. To speed this up, switch to another app and return to the kiosk. Bringing it to the foreground forces an immediate settings fetch.
4. The bar disappears when settings arrive. Until then, touch confirmation is blocked; scan instead.

Connection lost during a save

This is the hardest case: you submitted an operation and do not know if it reached the server.

• Replenishment asks the server for the current state and shows the yellow message “Network error — state refreshed / The last operation was not confirmed. Check the counter on screen before retrying.” Check the counter; do not retry blindly.
• Receiving is protected server-side: retrying uses the same identifier and cannot post the goods twice.
• Packing when booking a courier explicitly warns that the parcel may have shipped; check the parcels before retrying.

Company settings missing

This is different from losing the network: the terminal is connected but has not received company policy. It retries automatically at increasing intervals, up to once every 30 seconds. Touch confirmation is deliberately blocked because the terminal does not know company thresholds and permissions; it would rather deny an action than allow too much.