Skip to content

missing_or_contradictory queue is 16,7xx rows and now grows by design, needs an operator surface #40

Description

@rusholme

What the purpose requires

A queue that is designed to grow needs an operator surface or periodic
triage report — otherwise correct-and-growing-on-purpose is
indistinguishable from unattended and forgotten.

What exists today

Live count is 16,635 pre-fix (16,571 contradictory + 64 missing,
per LEDGER-preprove-db.md). Fix (b) for the CheckViolation
(18f046b2/42276e8f) deliberately routes non-representable rows here
instead of crashing, so the queue is correct and growing on purpose,
evidence intact — but nothing currently works it. Proposed: an operator
surface (rapidctl reconcile-stranded?) or a periodic triage report.

The trigger that reopens this

Before the queue is next cited in an incident review as either healthy
or alarming without a triage mechanism to back that claim, or once
queue size becomes large enough to affect query performance on the
attempts table.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    handoverHandover: outstanding at the 2026-09-13 documentation handover

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions