Stocktake 2026-11-21: re-verify 5 stale + 2 threshold pages against live state; freshness 0 stale; skills-index 299/67
This commit is contained in:
@@ -3,8 +3,8 @@ title: Mnemosyne Health Monitor auto-paused after gateway-connection failure
|
||||
type: incident
|
||||
status: resolved
|
||||
created: 2026-10-30
|
||||
updated: 2026-10-31
|
||||
verified_on: 2026-10-31
|
||||
updated: 2026-11-21
|
||||
verified_on: 2026-11-21
|
||||
confidence: high
|
||||
tags: [cron, mnemosyne, gateway, incident, delivery]
|
||||
sources: [live-jobs-json, live-executions-db, live-deliveries-db, live-cron-incidents]
|
||||
@@ -24,6 +24,15 @@ host outage** and fired late in the 16:37:21 catch-up burst, still `running` at
|
||||
|
||||
**Historical snapshot (2026-10-30 03:3x): ACTIVE** — the job is disabled, the incident row is open, and the failure notice never reached Telegram.
|
||||
|
||||
## Re-verification — 2026-11-21 (stocktake)
|
||||
|
||||
`ea79a2107e36` is still `enabled: true` and firing every 12 h, but `last_status: error`,
|
||||
`failure_streak: 4` — the monitor is (correctly) reporting the **Mnemosyne capture stall**:
|
||||
its latest run found a user message with no `working_memory` row and `last capture
|
||||
2026-11-18 11:25`. That is a live memory-pipeline fault the monitor is doing its job about, not a
|
||||
delivery or gateway fault → [[incidents/2026-11-14-mnemosyne-capture-stall]]. The 2026-10-30
|
||||
resolution above (auto-close, deliveries resumed) stands.
|
||||
|
||||
## Summary
|
||||
|
||||
The Mnemosyne Health Monitor cron job `ea79a2107e36` (`0 */12 * * *`, delivery topic `102`) failed its
|
||||
|
||||
Reference in New Issue
Block a user