User instructions

Connection & saves

Know what is local, confirmed or still uncertain

Open Connection & saves above the main browser workspace or Fleet portal. Opening this panel, checking the hub connection or reviewing a warning does not submit a form or finish work.

Connection is not a save confirmation

Connected to hub means this tab recently received a complete hub response. Not recently checked means that observation is older than 30 seconds. Hub not reachable can mean a stopped server, blocked network or unreadable response; it is not a diagnosis of internet availability. Wavelink does not test the internet. Local use needs access to the running hub, which may work without internet. Browser network and live-update indicators do not prove a save succeeded.

Work on this device

The main workspace separates queued checklist changes, conflicts, checklist drafts, log drafts, operation forms and a new-checklist draft. A form says Saving draft on this device while storage is pending and confirms the local draft only after that write completes. Local storage is tied to the existing browser profile and hub address. It is not a hub backup.

Only already-queued checklist changes retry automatically. Log, maintenance, inventory and other operation drafts still need review and an explicit Save. Opening the panel or using Check hub connection does not send them. A photo held in a draft is not hub evidence until its containing submission succeeds.

When the save outcome is uncertain

A timeout, lost response or server error can happen after the hub saves an action. The panel keeps a local request receipt marked Uncertain save result. Reconnecting, loading the record or successfully saving another action does not silently clear it.

1. Keep the original page and draft. Do not immediately create another receipt, placement, maintenance completion or stock movement.
2. Open the linked saved workspace and inspect the intended record and its history. Close or keep any existing edit form before using a navigation link.
3. Where the original form supports a stable operation ID, an explicit unchanged retry uses that same request identity. A confirmed response can resolve the receipt. A changed request is not the same retry, and an access/conflict rejection of a retry does not prove the first attempt failed.
4. When manual checking is necessary, choose I checked this result... only after checking the saved record. This records Reviewed — outcome not verified, not “Saved to hub”, and makes no operational change. It releases the local warning gate for a different action. Ask a manager when the physical or saved outcome cannot be established.

Wavelink blocks a different new request to the same unresolved action/target until review. It also prevents a second concurrent submission of the same request. Forms lock during a submission so a pending edit is not silently replaced by the response.

Fleet is still online-only for forms

Fleet receipts, placements, manifests and vessel-log forms need an explicit online save. They are not offline drafts or an automatic outbox. Fleet keeps request metadata in the current tab’s session storage, which can survive a same-tab refresh but is not durable form recovery and may be lost when that tab or browser session ends. Keep an uncertain form open and export its receipts before leaving.

Recovery, access and limits

The journal records action identifiers, request status and device-clock timestamps, not passwords, tokens, full forms or evidence. It is not a server audit trail or proof that a physical operation happened. The panel shows receipts scoped to the signed-in account and project; exports should still be handled as internal information. Main-workspace recovery exports include the receipt metadata with existing supported drafts. Fleet exports receipts only.