Skip to content
Drainproof
Demo mode. These reports are fixtures generated by running the Drainproof CLI against the bundled example policies. They are not results from your project.

← Scenario library

A submitted transaction with unknown outcome keeps counting

ambiguous-submission-keeps-counting

high

Description

If a transaction was submitted but its outcome is unknown (for example a network timeout), it may still execute. Its amount must keep counting toward the daily limit.

Remediation: Only release a reservation when the transaction is known to have failed.

state-concurrency · required · ../../packages/cli/templates/scenarios/state-concurrency/ambiguous-submission-keeps-counting.yaml

Outcomes across stored runs

  • Pass 3
  • Fail 0
  • Error 0
  • Skipped 1

Execution history

Most recent steps

No steps were executed (target "naive-guard" does not support: lifecycle).