2026-11-18 stocktake: re-verify 7 stale pages against live state, resolve gmail-digest refire incident
This commit is contained in:
@@ -3,8 +3,8 @@ title: Gateway Exited Uncleanly on 2026-10-20 — One Cron Run Orphaned (status
|
||||
type: incident
|
||||
status: active
|
||||
created: 2026-10-21
|
||||
updated: 2026-10-27
|
||||
verified_on: 2026-10-27
|
||||
updated: 2026-11-18
|
||||
verified_on: 2026-11-18
|
||||
review_after: 2026-11-03
|
||||
confidence: high
|
||||
tags: [gateway, cron, scheduler, lifecycle, restart, silent-failure]
|
||||
@@ -36,6 +36,8 @@ gateway exit since 2026-09-21.
|
||||
| 09:09:16 | log line `Starting Hermes Gateway...` (the running process reports start time 08:55:09 — the two disagree by ~14 min, so the restart instant is not pinned to the second) |
|
||||
| ~09:10 | the orphaned execution row closes as **`unknown`** |
|
||||
|
||||
> **Re-verified 2026-11-18 — no recurrence in the retained window.** Zero `status: unknown` executions exist in the retained `executions.db` (retention floor ~18 d, so the 10-20 row itself has aged out — its facts below stand on the 10-27 read). Retained `gateway.log*` files carry no UNCLEANLY line newer than **2026-08-31** (log rotation has since dropped the 10-20 entry the ledger once showed; per that rotation, `0` means *not in the retained window*, not *never happened*). Zero unclosed `cron_incidents` rows. Status unchanged — the silent-orphan failure mode still has no alerting of its own.
|
||||
|
||||
## Impact
|
||||
|
||||
- **The 2026-10-20 Gmail Action Digest has no delivery row in `deliveries.db` and its execution carries
|
||||
|
||||
Reference in New Issue
Block a user