Window 2026-11-10 23:59 -> 2026-11-11 23:59 (two windows: the 11-10 audit failed). NEW incident: incidents/2026-11-10-wiki-audit-429-all-targets-skipped.md - cbfe434a3b5e ran 23:59:54.486572 -> 2026-11-11 00:12:29.646987 = 12m35s, failed, delivery suppressed - RuntimeError: HTTP 429 ... all targets skipped by pre-dispatch filters (credits 100% conn:3021bab6) reset after 6h24m31s; 6 candidates, attempted 0; tenant tn-5ud77abtl1 quota exceeded - incident row cbfe43_ed01845310d8 (rate_limit) alerted_at NULL, closed_at NULL = only open row - consequence: the 2026-11-10 window was never audited; non-clean last_status 1 -> 2 RESOLVED with output (dated Recovery sections added): - stocktake 1a8e90ea2271 03:00:56.081504 -> 04:11:38.724852 = 1h10m42s, 36 stale re-verified -> 0 - job radar stage1 07:01:08 -> 07:37:34 = 36m26s, first handoff since 2026-11-06 (22,682 B) - radar stage2 recovery fire 07:35:56 -> 08:03:47 closed row 5fc292_773822455856 resolved UPDATED pages: current-state.md, systems/scheduled-tasks.md, systems/opencode-go.md (opencode-zen 401 api_key_expired now observed 7x, paired with nous 404 credits 14x), incidents/2026-10-22-nous-portal-refresh-token-invalid.md, index.md, log.md
95 lines
6.6 KiB
Markdown
95 lines
6.6 KiB
Markdown
---
|
|
title: "2026-11-09 — Stocktake Completes With Zero Edits"
|
|
type: incident
|
|
status: resolved
|
|
created: 2026-11-10
|
|
updated: 2026-11-11
|
|
verified_on: 2026-11-11
|
|
confidence: high
|
|
tags: [cron, wiki, stocktake, tool-budget, silent-failure, omni-101, free-stack]
|
|
sources: ["executions.db (1a8e90ea2271: 2026-11-09T03:00:43+08:00 → 2026-11-09T12:10:47+08:00, status completed, delivery_outcome suppressed)", "~/.hermes/cron/output/1a8e90ea2271/2026-11-09_12-10-46.md (8,305 bytes; RUN INCOMPLETE, \\u201ctool-iteration budget exhausted during verification\\u201d)", "cron_incidents (1a8e90_628d914f1f97, 1a8e90_2f370ef764f5, 1a8e90_a9cad99cb150 — all closed 2026-11-09T12:10:47.125205+08:00)", "wiki-stocktake-maintenance job 1a8e90ea2271 (provider custom:omni-101, model free-stack)"]
|
|
---
|
|
|
|
# 2026-11-09 — Stocktake Completes With Zero Edits
|
|
|
|
## Summary
|
|
|
|
The nightly wiki stocktake (`wiki-stocktake-maintenance`, `1a8e90ea2271`) ran on 2026-11-09 from **03:00:43 to 12:10:47** — **9 h 10 m** — and the harness recorded it **`completed`** with delivery `suppressed`. Its own output file records the opposite: the run ran out of tool-iteration budget inside its verification phase, applied **zero edits**, made **no commit**, and its findings never landed.
|
|
|
|
**This is the third consecutive day the stocktake's work did not land** — 11-07 died at 2 h 02 m, 11-08 at 1 h 35 m (both `failed`), 11-09 at 9 h 10 m (`completed`). The visible status this time is *worse*, not better: `failure_streak` fell **3 → 0** and `last_status` shows **ok**, while the work stayed undone.
|
|
|
|
## Timeline (AWST, 2026-11-09)
|
|
|
|
| Time | Event |
|
|
|---|---|
|
|
| 03:00:43 | Run starts (`1a8e90ea2271`) |
|
|
| ~04:1x | Tool-iteration budget exhausted during verification; output file written with `RUN INCOMPLETE` |
|
|
| 12:10:47.125205 | Harness closes the run — `completed`, delivery `suppressed` |
|
|
| 12:10:47.125205 | The **three** long-open stocktake incident rows close at the same instant: `1a8e90_628d914f1f97` (11-07T04:29:54), `1a8e90_2f370ef764f5` (11-07T05:02:21), `1a8e90_a9cad99cb150` (11-08T04:35:38) |
|
|
|
|
## Root Cause
|
|
|
|
Same family as 11-07/11-08: **the run spends its entire tool budget before reaching the write phase.** The run's own output file records the stop as the tool-iteration budget being exhausted **during verification**, with zero edits applied — the edits it had identified were never written.
|
|
|
|
Secondary cause (confirmed again this window): the job is pinned to `custom:omni-101` / **`free-stack`** — a combo recorded broken on **2026-08-14** (see [[systems/scheduled-tasks]]).
|
|
|
|
## Evidence
|
|
|
|
- `executions.db`: `started_at 2026-11-09T03:00:43+08:00` → `finished_at 2026-11-09T12:10:47+08:00`, `status completed`, `delivery_outcome suppressed`. Previous two runs: 11-08 `failed` (03:01:11 → 04:36:08, 1 h 35 m), 11-07 `failed` (03:00:31 → 05:02:22, 2 h 02 m).
|
|
- Output file `/home/hermes/.hermes/cron/output/1a8e90ea2271/2026-11-09_12-10-46.md` (8,305 bytes) ends `RUN INCOMPLETE`, with the tool-iteration budget exhausted inside verification.
|
|
- The three stocktake incident rows all carry `closed_at = 2026-11-09T12:10:47.125205+08:00` — i.e. they closed on **completion**, not on a fix. All three have `alerted_at = null`: they never alerted.
|
|
- Git: **no stocktake commit on 11-09** — zero edits were applied, so there was nothing to commit and nothing to revert. (On 11-07/11-08 the page was left dirty and then reverted; on 11-09 no edit was ever made.)
|
|
|
|
## Impact
|
|
|
|
- Nine consecutive stalled stocktake runs (11-01 … 11-09) — the nightly wiki freshness pass is producing no durable output.
|
|
- The stocktake's *top-priority* brief item on 11-09 was the **monotonically worsening failure streak** itself. The job closed its own incident while failing that item, which is the failure mode to watch: **`completed` and `ok` now overstate the stocktake's health.**
|
|
- Three incident rows were silently cleared, so the fleet's incident board now reads **0 open** while the underlying problem is unfixed.
|
|
|
|
## Fix Applied
|
|
|
|
**None — this is a detection-and-verification record.** The page documents the failure and the misleading status so the next audit starts from truth.
|
|
|
|
Also recorded this window: the `free-stack` pin on `1a8e90ea2271` — the only deterministic configuration fault in the chain — is **still in place**, unchanged from the 11-08 record.
|
|
|
|
## Prevention
|
|
|
|
- **Alerting must fire on write progress, not completion.** This run produced 2 of 3 failure days silently and the third day produced a run that reported success while editing nothing. A check on `commit_count` / `edits_applied` for this job would have caught all three.
|
|
- Don't read `status`/`failure_streak` as the stocktake's health. Read whether a commit landed.
|
|
|
|
## Recovery — 2026-11-11: the pass ran in 1 h 10 m and landed 36 pages
|
|
|
|
The next scheduled slot **worked**, and worked quickly:
|
|
|
|
| Field | 11-09 (this incident) | **11-11** |
|
|
|---|---|---|
|
|
| Window | 03:00:43 → 12:10:47 | **03:00:56.081504 → 04:11:38.724852** |
|
|
| Duration | **9 h 10 m** | **1 h 10 m 42 s** |
|
|
| Terminal state | `completed` / `suppressed` | `completed` / `suppressed` |
|
|
| Edits landed | **0** | **36 stale pages re-verified → 0 stale** |
|
|
| Commit | **none** | **`341dda9`** + **`c108eb1`** |
|
|
| Freshness report | — | `raw/stocktake/freshness-20261111.txt` (**6,235 B**) |
|
|
|
|
- `341dda9` re-verified 30+ further pages live and de-flagged them, and applied real content
|
|
corrections — the live fallback chain rewritten in [[runbooks/test-openrouter]] (primary back to
|
|
`smart-route` / `custom:omni-101`), the CT333 `clawtest` naming claim corrected, and the nous
|
|
**404 `insufficient_credits_for_paid_model`** signature replacing the old refresh-token reading in
|
|
[[incidents/2026-10-22-nous-portal-refresh-token-invalid]].
|
|
- `c108eb1` regenerated the freshness report after the log/index addendum, so the published Quartz build
|
|
matches HEAD.
|
|
- **Job state:** `last_status: ok`, `failure_streak` 0, `last_run` 2026-11-11T03:00:56.
|
|
⚠ The job is **still pinned to `custom:omni-101` / `free-stack`** — the combo recorded broken on
|
|
2026-08-14 — and this run succeeded on it anyway. That is an observation, not a repin.
|
|
|
|
**Status: `resolved`.** The 11-07/11-08/11-09 run of failures is closed by output, not by a cosmetic
|
|
`failure_streak` reset. The page's own prevention rule stands: *alert on `commit_count` / `edits_applied`,
|
|
never on `status`* — this recovery is exactly why it matters, because 11-09 and 11-11 both read
|
|
`completed` / `suppressed` and only one of them did anything.
|
|
|
|
## Related
|
|
|
|
- [[systems/scheduled-tasks]]
|
|
- [[infrastructure/tailscale]]
|
|
- [[incidents/2026-11-08-pre-tool-call-hook-timeout-cascade]]
|
|
- [[incidents/2026-11-09-job-radar-stage1-stall-silent-noop]]
|