Skip to main content

DEBT.LEDGER_UNREADABLE — the account is present and this build cannot act on it

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit, deploy

The debt ledger is on this machine and this build cannot use it — malformed JSON, a shape it does not recognize, a schema version newer than the one it writes, or an acknowledged entry with no reason.

Why it is not the same finding as a missing account​

Because the next move is different. A missing file is a deployment or a path problem; a present one that cannot be parsed is a content problem, usually in a specific line. Sharing one finding would send half the readers to the wrong place.

The usual causes​

  • A newer SQLens wrote it. The schema version is explicit precisely so an older build says so instead of guessing.
  • A merge left conflict markers in it.
  • An acknowledgment with no reason. The state means somebody made a decision; without the decision written down it is a suppression nobody argued for, and it is refused rather than honored.

What it does not mean​

The audit itself is unaffected. Every other rule ran and every other finding stands — only the debt account could not be consulted.