Incidents

An incident is created when the marketplace cannot confirm delivery, restoration, a game-asset change, transfer, or payout. It is not a normal form error and does not complete a financial operation by itself.

Incomplete operations requiring inspection or a controlled retry

Investigate an incident

1. Open the related operation and identify its last confirmed stage.
2. Verify the actual game asset, reservation, or external payout state.
3. Compare the failure code and attempt log with the observed result.
4. Resume only after confirming that retrying is idempotent.
5. Record the verified resolution and confirm the incident is no longer open.

Related operation, stage, diagnostics, and attempt history

Verified recovery

For an uncertain delivery outcome, choose a decision only after verifying game state: confirm delivery, retry it, or cancel and refund the order. The resolution note records what the operator actually checked.

The operator decision resumes the existing operation without creating a duplicate

Resolve critical open incidents before publishing new rules or resuming operations in bulk.

Notes and descriptions

Recovery notes support emphasis, lists and links. Describe the checks you performed and the expected result so another team member can understand the decision.