Scope
Oto prevents repeated or interrupted requests from creating duplicate payments, wallet entries, redemptions, attendance, stock changes, issuance, occupancy changes, or child-release outcomes.
Design
When an important action is repeated or interrupted, Oto shows its known result. Users can retry or reconcile only where the applicable workflow allows it. Approved branch-local workflows show whether locally completed work still requires confirmation or synchronization.
Failure handling
An uncertain action is not shown as successful and is not repeated blindly. The user sees whether it failed, remains pending, or requires review.
Requirements
- Prevent duplicate payments, wallet spending, booking redemption, attendance, stock changes, issuance, occupancy changes, and child release.
- Show completed, failed, pending, or unresolved states where the applicable workflow requires them.
- Do not repeat an uncertain payment, redemption, release, or other consequential action without confirmation.
- Support the branch-local continuity explicitly required by hardware workflows.
Verification
- Test repeated and interrupted payments, wallet spending, booking redemption, attendance, stock changes, issuance, occupancy changes, and child release.
- Test the visible pending, unresolved, retry, and reconciliation behavior required by applicable workflows.