A submitted transaction with unknown outcome keeps counting
ambiguous-submission-keeps-counting
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
- run_317318f32026-11-06 20:03 UTCSkipped
- run_b271aaff2026-11-06 20:03 UTCPass
- run_28b022e22026-11-06 20:03 UTCPass
- run_34e4198a2026-11-06 20:03 UTCPass
| Run | Started | Outcome |
|---|---|---|
| run_317318f3 | 2026-11-06 20:03 UTC | Skipped |
| run_b271aaff | 2026-11-06 20:03 UTC | Pass |
| run_28b022e2 | 2026-11-06 20:03 UTC | Pass |
| run_34e4198a | 2026-11-06 20:03 UTC | Pass |
Most recent steps
No steps were executed (target "naive-guard" does not support: lifecycle).