Historical cron failure holds readiness at FIX until next scheduled run
brain-distill · confidence medium · status active
tags: hermes cron readiness remediation ops
On 2026-08-28 Hermes cron readiness reported FIX bad=1 across seven remediation sweeps over 11 hours. Sole cause: a historical TERMINAL_CWD write-lock timeout (job 1717d5a51126, 660s) already recorded in failed output. Gateway, scheduler, and health probes were live throughout; no active lock-holder or stuck process existed. Readiness clears only when the job completes its next scheduled run successfully. Rule: when failed output shows a terminal historical error and live probes are healthy, record evidence once, confirm the job is enabled with the correct route, wait for the next scheduled run, and stop re-sweeping. Distinct from the 2026-07-09 stale-FIX lesson, where the report was stale but the job had already recovered.
Sources:
/Users/dwayne/clawd/memory/health-remediation.log