MC-4432 — [watchdog:missed:cron-watchdog] Task didn't fire: cron-watchdog

Home Board MC-4432

[watchdog:missed:cron-watchdog] Task didn't fire: cron-watchdog

Task `cron-watchdog` (Cron watchdog — Telegram alert for overdue tasks) has a cron schedule of `*/30 * * * *`. The previous expected fire was at **2026-05-30 08:30 UTC+02:00** (...

State Done Next Action Closed Owner Luci Runtime Closed Age 14d ago

Description

MC-4432

Task `cron-watchdog` (Cron watchdog — Telegram alert for overdue tasks) has a cron schedule of `*/30 * * * *`. The previous expected fire was at **2026-05-30 08:30 UTC+02:00** (more than 15 min ago), but `task_runs` has no entry since then. Last actual run: **2026-05-30 07:01:10** Task file: `~/workspace/tasks/cron-watchdog.md` Investigate: is the task enabled? Is the schedule correct? Is there a lock or prerequisite blocking it?

Activity

done

Luci is working...

Details — Done · Medium · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source scheduler-watchdog (scheduled)

Project infra

Created 14d ago

Updated 14d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. ticket_runtime_done profile claude_opus_1m_high · cwd /home/lucienne/workspace/.claude/worktrees/pool-0 · uptime 14d 1h · last activity 13d 23h ago MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here. Raw console: luci · claude/anthropic/opus[1m]

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

Luci 14d ago

cron-watchdog miss root-caused to scheduler-wide flock starvation: investment-weekly-digest ran inline 6587s (~1h50m NotebookLM) holding /tmp/scheduler.lock, blocking all tasks 07:01-08:51. Fixed by marking it background:true (committed master 6e3b42c2). cron-watchdog itself fine — enabled, schedule correct; self-recovered 08:52.

luci 14d ago

Workflow action `review_ready` applied. Work ready for review.

orchestrator-board-sweep 14d ago

Auto-closed by orchestrator board-sweep: the underlying scheduled task `cron-watchdog` has recovered — task_runs shows a successful run after this missed-fire ticket was raised. The watchdog condition no longer holds.

luci 14d ago

Shadow reviewer verdict: FAIL (advisory only). Ticket was gated to done by the orchestrator/operator — not reopening; the gate is authoritative. Reasons: The ticket MC-4432 requires investigating why the `cron-watchdog` task missed its scheduled run and fixing it. The worker claims to have fixed it by marking `investment-weekly-digest` as `background:true` in commit 6e3b42c2. However, the provided diff is for an entirely unrelated change to `scripts/mc_auto_review.py` (done_sha=f7d3080c), which modifies oversize-diff incident handling. The actual fix for the cron-watchdog issue is missing from the committed changes, meaning the core requirement has no verifiable implementation in this diff. Gaps: - The committed diff does not contain the fix for the `cron-watchdog` missed fire (the `background:true` change to `investment-weekly-digest`). - No tests or evidence are provided in the diff to verify the scheduler lock starvation fix.

luci-control-room 14d ago

Control Room terminal metadata corrected. The shadow-review FAIL was based on stale/wrong `done_sha` metadata (`f7d3080c`), not the actual scheduler-starvation fix. Verified `6e3b42c2` is on `origin/master`, contains `background: true` for `tasks/investment-weekly-digest.md`, and `cron-watchdog` recovered (09:00 run: 0 overdue). Leaving ticket closed and replacing `done_sha` with the verified landing SHA. Human input required: no.