OVERRIDES runtime profile: uses notify.py (urllib direct Telegram) because
this watchdog never invokes the claude CLI — pure HTTP poll + alert.
Every 30 min, hits MC's /api/v1/scheduler/inspect and alerts Telegram (MC
forum topic) for any task overdue by more than 2× its cron interval. Skips
tasks marked disabled or runtime_profile: manual. Dedup'd per task at
1-hour cadence so a stuck task pings at most once per hour.
Complements scheduler-watchdog.md (creates MC tickets for various failure
modes) — this one is the fast Telegram side-channel so Elmar sees stuck
schedules within a single cycle rather than at the next hourly watchdog tick.
Implementation: ~/workspace/scripts/cron_watchdog.py.
Ticket: MC-3306.
. ~/.claude/env/api_keys.env 2>/dev/null; python3 /home/lucienne/workspace/scripts/cron_watchdog.py
Format: minute hour day month weekday
| Started | Status | Duration | Log |
|---|---|---|---|
| 11m ago | completed | 0s | View log |
| 41m ago | completed | 0s | View log |
| 1h ago | completed | 0s | View log |
| 2h ago | completed | 0s | View log |
| 2h ago | completed | 0s | View log |
| 3h ago | completed | 0s | View log |
| 3h ago | completed | 0s | View log |
| 4h ago | completed | 0s | View log |
| 4h ago | completed | 0s | View log |
| 5h ago | completed | 0s | View log |
| 5h ago | completed | 0s | View log |
| 6h ago | completed | 0s | View log |
| 6h ago | completed | 0s | View log |
| 7h ago | completed | 0s | View log |
| 7h ago | completed | 0s | View log |
| 8h ago | completed | 0s | View log |
| 8h ago | completed | 0s | View log |
| 9h ago | completed | 0s | View log |
| 9h ago | completed | 0s | View log |
| 10h ago | completed | 0s | View log |
| 10h ago | completed | 0s | View log |
| 11h ago | completed | 0s | View log |
| 11h ago | completed | 0s | View log |
| 12h ago | completed | 0s | View log |
| 12h ago | completed | 0s | View log |
| 13h ago | completed | 0s | View log |
| 13h ago | completed | 0s | View log |
| 14h ago | completed | 0s | View log |
| 14h ago | completed | 0s | View log |
| 15h ago | completed | 0s | View log |
| 15h ago | completed | 0s | View log |
| 16h ago | completed | 0s | View log |
| 16h ago | completed | 0s | View log |
| 17h ago | completed | 0s | View log |
| 17h ago | completed | 0s | View log |
| 18h ago | completed | 0s | View log |
| 18h ago | completed | 0s | View log |
| 19h ago | completed | 1s | View log |
| 19h ago | completed | 0s | View log |
| 20h ago | completed | 0s | View log |
| 20h ago | completed | 0s | View log |
| 21h ago | completed | 1s | View log |
| 21h ago | completed | 0s | View log |
| 22h ago | completed | 1s | View log |
| 22h ago | completed | 0s | View log |
| 23h ago | completed | 0s | View log |
| 23h ago | completed | 0s | View log |
| 24h ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
Mission Control is the board for your delegated work: requests come in, Luci coordinates the next step, and evidence stays visible for review.
Luci is your always-on assistant for routing, status updates, and follow-through. Operators can still open deeper evidence when needed.