Archived outcome_unknown actions are kept forever #9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The live store holds 114
outcome_unknownactions from 2026-09-20 to 2026-09-26, all from the old China vs USA scenario:navigation.set_speedhosting.launchengagement.requestnavigation.set_altitudemissions.createThey are past
ARCHIVED_HOLD_SECONDS, so they no longer block a repeat. They can never be read back, and retention keeps them under the owner decision to keep unsettled game effects with what they name. Until PR #1,/api/v1/metricscounted them asunresolved: 114. It now reportsunresolved_blockingandunresolved_archived_expiredseparately.Decision needed: a terminal state (for example
expired_unverifiable) for an archived unknown action once its hold has passed and its timeline is gone, so retention can delete it and its reservations.The mix also shows where unknowns came from:
Newer guards address some of these, for example the grouped-movement guard of 2026-10-01.
Found in the 2026-10-13 review (PR #1).
Done in
c5b410d(0.7.1), now on master. An unresolved action of an archived session is closed asunverifiable(final: never established, never retried) once its 30-minute hold has passed. Its reservations are released, and retention removes it along with what it kept. On the live store all 114 were closed on 2026-10-13 at 15:06:03Z, and their 18 earlier sessions were cleaned up by 15:06:44Z. Metrics now show 0 unresolved actions and 0 reservations.