Offline Ticket Check-In Failure Drill
Test disconnected scans, stale data, local queues, retry, cross-device conflicts, reconnect, and reconciliation.
Why this work needs a system
Offline mode trades immediate shared truth for continuity. Each device may act on stale data, and two gates can accept the same code before synchronisation resolves the conflict.
The useful test is whether another authorised team member can see what happened, what should happen next, and which exception still needs attention. A tool helps only when the operating rule is clear enough for people to follow under pressure.
A practical workflow
From preparation to review
- 01Baseline
Synchronise current test data and record time, device, app, event, and pending count.
- 02Disconnect
Remove connectivity deliberately and confirm the operator sees the offline state.
- 03Exercise
Scan valid, duplicate, revoked-after-sync, and cross-device conflict scenarios.
- 04Reconnect
Observe queue replay, retry, idempotency, and explicit conflict handling.
- 05Reconcile
Compare device history, server timeline, reports, and unresolved items.
Operating checklist
Use this before rollout
- Test data cannot admit a real guest
- Offline state is visible
- Queue persists through app restart
- Same scan is not duplicated on retry
- Stale revocation policy is documented
- Cross-device conflict is exercised
- Failed sync has an operator recovery path
Limits and failure modes
Where Nox-Tickets fits
Nox-Tickets provides the product surface for this workflow, but configuration does not replace ownership, training, exception policy, or live verification. Review the current capability and status pages before relying on it in production.