Skip to content

Issues and Repairs

Problems in production data: what is still wrong and needs fixing, and the record of each
repair that was carried out. Anyone can add a page.

To fix

Page Area Ticket What is still wrong
Ledger leftovers after BAN-348 Ledger BAN-348 43 credit-card flows, 1,888 stale holds and 693 accounts whose reserve differs from their flow holds

Repaired

Page Area Ticket Carried out
Ledger repair after BAN-306 Ledger BAN-348 2026-10-06 to 2026-10-08
Galileo flow repair Ledger BAN-306 2026-09-03 to 2026-09-09

Adding a page

  • One page per issue or repair, named after it and its ticket, for example
    Ledger-Leftovers-BAN-348.md, and listed in the matching table above.
  • An open issue's page starts with Status: to fix. and says, per item, what is wrong, why
    it is still open, what fixing it takes and how current the numbers are. When it is fixed,
    move its row from To fix to Repaired.
  • A repair's page records what was wrong, what was done, what it changed for customers and
    what was checked afterwards.
  • Attachments such as standalone HTML pages go in a folder named after the ticket, next to the
    page, and are linked from it.
  • Account ids, flow ids and amounts are fine; no names, email addresses or phone numbers.