Offline sync conflicts
Review server-rejected handheld intents and independently choose revalidation or discard without editing the original payload or treating queued work as confirmed stock.
Screen orientation
The Sync conflicts route is available to eligible Stores Supervisor and Tenant Admin roles with offline_intents:review. The originating operator cannot review their own conflict. Retry executes through the original operator's current authority, not the reviewer's transaction permissions.
Awaiting-review and discarded metrics precede unresolved server conflicts and up to twenty displayed discarded entries. Review conflict opens a dialog containing the server rejection, one editable evidence/decision note and Retry or Discard actions. This is not the handheld's local queue editor.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Transaction summary / Intent type | Read-only conflict heading | Captured with the original intent. | Identify the intended receipt, kit issue, transfer dispatch/receipt or cycle-count submission before reviewing the rejection. | Explains which existing transaction handler will be revalidated. |
| Server rejection | Read-only reason | Shown for unresolved conflicts and in the review dialog. | Investigate the reported current-stock, state, scope, clearance or independence failure through the owning record. | Explains why the intent has not been confirmed. |
| Idempotency key | Read-only identifier | Retained for each intent. | Use the same key to correlate handheld and server status; this screen does not create a replacement key. | Preserves intent identity across replay attempts. |
| Operator / Device | Read-only context | Captured with the intent. | Confirm the originating operator and device. Do not assume the supervisor's authority replaces the operator's current access. | Identifies custody responsibility and replay identity. |
| Queued time / Attempt count | Read-only metadata | Captured queue time and server replay count. | Use these to understand delay and previous attempts, not as proof of a physical or ledger transaction. | Shows the history of attempted synchronisation. |
| Review evidence and decision note | Text | Required for Retry or Discard; 10–1000 characters. | Record the checked facts, custody-owner coordination and reason for retrying or discarding. This is a decision note, not a document-upload control. | Retains an attributable independent supervisor decision. |
| Discarded resolution note / Reviewer | Read-only reviewed history | Present for discarded intents. | Read the recorded rationale and independent reviewer before taking any separate corrective action. | Preserves evidence of intentional non-posting. |
Actions and effects
When to use: For an unresolved server CONFLICT.
What it does: Opens the evidence and decision dialog; does not retry or post the original action.
When to use: By a different authorised reviewer after the cause has been addressed and a decision note recorded.
What it does: Replays the retained payload as the active original operator against current stock, scope, clearance and segregation-of-duties checks. Only successful handler validation can confirm it; failure can return a conflict.
When to use: By a different authorised reviewer when the intended action must not be posted.
What it does: Marks the intent DISCARDED with retained note and reviewer. Does not delete evidence, undo physical activity or reverse an earlier valid transaction.
When to use: Before a decision is posted.
What it does: Closes the dialog and leaves the conflict unresolved.
Lists and states
- Unresolved server conflicts: summary, intent type, reason, idempotency key, originating operator, device, queued time and attempts identify work awaiting explicit review.
- Discarded after review retains summary, resolution note and reviewer. The server returns up to 200 conflict/discarded records; the screen displays up to twenty discarded entries, not a complete audit export.
Authority boundary
Queued is not confirmed. Retry does not force success, edit the payload or borrow supervisor transaction authority; it runs as the original operator. Discard retains evidence and performs no stock reversal. Corrections requiring different transaction data belong in the owning workflow.