An uncertain answer means the browser does not yet know whether the server accepted the action. It is different from a definite rejection. Keep the physical unit controlled and stop further entries until the result is settled.
Settle the existing action
When a timeout, lost connection or server error makes a command uncertain, the page disables changes and keeps its original request for reconciliation. Use the offered check or reconciliation action. Do not open a new attempt or resend the same physical work with a newly created identity.
A confirmed accepted receipt means use the recorded result. A confirmed not-applied outcome means review current work and follow the offered next action. A definite rejection must be addressed for its stated reason; repeating the old command does not make changed conditions satisfy it.
The station does not provide an offline evidence queue. An offline page is not permission to record work later as if the server had accepted it at the original time. Note the physical situation through your site's normal exception process and ask the Supervisor how to proceed.
Resolve control conflicts
If another station holds the work, arrange a deliberate handover. A live claim is not silently stolen. A later valid claim or supervised transfer makes the earlier station's control stale. Refresh before doing anything else and confirm who physically holds the unit.
A session can end because a station was retired, your local assignment changed or the application entered recovery. Ask the Supervisor and Owner to check the reason. Restoring a role does not establish what work happened during the interruption.
Unlock your own station
After inactivity, the station may show its lock screen. Sign in again through Accounts as yourself and choose the station again. Check whether the work still needs to be claimed. A heartbeat keeps a live claim active but is not operator activity and does not prevent the inactivity lock indefinitely.
For a rejected identifier, compare the exact read, including spaces and leading zeros, with the physical label and the intended unit. Check scanner suffix behaviour using the scanner test. Do not trim or change values to force acceptance.
Escalate with the site, station, unit, attempt, last known accepted action, displayed refusal and approximate time. Keep credentials and sensitive evidence out of general feedback. For identity problems, use Accounts access problems.
Record a scanner comparison
Open Scanner test from the station. Type the exact printed code into the first field, focus the second field and scan the same label. Read Received, the exact-match result and the listed prefix or suffix keys, including Enter or Tab. Timing is informational; it does not establish whether the input was typed or scanned.
With a station selected and an expected code entered, use Record this result for the named station. Check the station name and the recent test entry. A mismatch should lead to a check of the scanner's prefix, suffix and keyboard layout settings before production scanning. The test compares keyboard input and retains a profile; it does not qualify barcode durability or physical scanner performance.