audit 2026-11-06 (window 2026-11-05): incident ledger emptied 3 -> 0, first zero-failed day since 11-02, both 11-04 casualties recovered; NEW OPEN incident - live .env values verbatim in 17 mnemosyne rows, the 1.7 GB session store and two enabled Facebook Birthday prompts; freshness 0 stale / 124 fresh / 3 no-date of 127

This commit is contained in:
Tony0410
2026-11-06 00:29:52 +08:00
parent 2f3fc9952b
commit eba8062735
9 changed files with 460 additions and 22 deletions
@@ -1,10 +1,10 @@
---
title: Job Radar Stage 1 Died on a Provider Stream Timeout (2026-11-03) — Second Consecutive Day Without a Handoff
type: incident
status: open
status: resolved
created: 2026-11-04
updated: 2026-11-04
verified_on: 2026-11-04
updated: 2026-11-06
verified_on: 2026-11-06
review_after: 2026-11-11
confidence: high
tags: [cron, job-radar, stream-timeout, silent-failure, notion, context-compaction]
@@ -109,6 +109,18 @@ the pattern, not because the link is proven.
5. Should a stream timeout on a *file-deliverable* job trigger an automatic retry instead of leaving the
day's discovery to the next slot?
## Resolution (2026-11-06 nightly audit; live read 2026-11-06 00:3x AWST)
- The last open row raised here, `dca848_dfd4bea84f2a` (`timeout`, opened **2026-11-03 13:28:51**), **closed on
2026-11-05 at 12:36:17** - together with its 11-04 successor row `dca848_3b1bb1e9b003`.
- The job behind it, `dca8482e4f76` (**Daily Marketing Job Radar - Discovery**), **completed** its 2026-11-05
07:00 run in **5 h 35 m 35 s** (07:00:42 -> 12:36:18), with no repeat of
`RuntimeError: Upstream stream failed before completion.`
- **Status -> `resolved`.** The underlying questions (whether the 65 m 21 s stream silence is the watchdog
threshold or a silently dead socket; whether a stream timeout on a file-deliverable job should retry
automatically) remain open in [[systems/scheduled-tasks]] - they are no longer tracked as an incident
against this window.
## Related
- [[incidents/2026-11-02-job-radar-stage1-iteration-cap-recurrence]]