Stop recording when CheckStation reports uncertain command state, a station idle lock or changed inspection control. Keep the physical unit identifiable and tell the Supervisor what was last known to be accepted.
Settle the original action
Use the command panel's offered reconciliation or original-request action. It retains the same command identity and payload. A timeout does not establish that the operation failed; the server may have committed a reading, completion or decision before the answer was lost.
If the receipt confirms acceptance, use that recorded result. If the server confirms it was not applied, inspect the current attempt before following the next permitted action. A conflict or authority refusal must be resolved rather than bypassed with another identity.
Do not create a new unit, attempt or replacement reading solely to obtain a success message. Do not use a colleague's session to settle your request as though they were you.
Restore station control
Read the named station and current occupancy. A passed idle deadline is not silent takeover permission. Use the explicit takeover control, with fresh authentication and current occupancy details, only after arranging the physical handover.
If the attempt belongs to another station session, Resume under this station requires a reason and the appropriate current authentication. That action invalidates the previous control. The earlier operator must stop entering data.
For Station idle lock, use Refresh station control and reauthenticate when instructed. Check current source, attempt and control before recording further observations. A heartbeat or an old open form is not a permanent right to operate the station.
Distinguish input from quality failures
An invalid numeric format, wrong unit or excess precision is a refused entry, not a physical failure. A valid measured value outside the approved limit is retained as a failure and must not be erased by rescanning or retyping.
A source change, withdrawn plan, revoked instrument or restore barrier needs its specific supervised review and restart path. A reload cannot make those references valid again.
Escalate with the unit code, namespace, attempt, station, approximate time and exact visible refusal. Keep private readings and files within the approved support process. Use Accounts access problems for sign-in issues and manual readings for entry rules.
Prepare a technical support diagnostic
An Owner or Supervisor can open System health to read current technical checks and work needing attention. Passing technical checks do not qualify an inspection method or physical device.
The Owner can use Support diagnostic, select Diagnostic history period and choose Download support diagnostic. The choices are current state only, 7 days or 30 days. Review the JSON file through your approved handling process before providing it to support. Downloading it does not send it to anyone or change an inspection.