audit(2026-11-11) follow-up: settle the incident-ledger row count and note acked_at is NULL
This commit is contained in:
@@ -46,9 +46,12 @@ The three log lines from the run's own session `local-1000c1a3…` show the shap
|
||||
## Incident row — raised, never alerted, still open
|
||||
|
||||
`cbfe43_ed01845310d8` — `job_id cbfe434a3b5e`, `failure_type: rate_limit`, state **`detected`**,
|
||||
`alerted_at: NULL`, `closed_at: NULL`, opened **2026-11-11T00:12:28.578435+08:00**.
|
||||
`alerted_at: NULL`, `acked_at: NULL`, `closed_at: NULL`, opened **2026-11-11T00:12:28.578435+08:00**
|
||||
(`first_seen_at` = `last_seen_at` = that instant — seen exactly once).
|
||||
|
||||
- It is the **only open row** in `cron_incidents` (135 rows total) — the previous open item,
|
||||
- It is the **only open row** in `cron_incidents` — the table held **135** rows at audit time and **137**
|
||||
by the end of this run. `acked_at` is **NULL** as well as `alerted_at`, so nothing was told and
|
||||
nothing was acknowledged. The previous open item,
|
||||
`5fc292_773822455856`, closed `resolved` at **2026-11-11T08:03:47.644226**.
|
||||
- So the estate's single outstanding incident is **the audit's own failure**, and nothing was told
|
||||
about it.
|
||||
|
||||
Reference in New Issue
Block a user