Problem Statement

When autonomous reminders fail to execute (due to stuck sessions, trust zone errors, delivery failures, etc.), operators have zero visibility into the failure. There is no Slack notification, no dashboard, no execution history — only manual daemon log inspection reveals the issue.

Evidence

On June 25, 2026, a single reminder (gotowebinar-triage-automation) failed silently 49 times in one day due to a stuck session blocking the duplicate guard. Not a single operator noticed until manual investigation.

Daemon Log Evidence

The only signal is a warning in daemon logs:

[WRN] ... reminder_skipped_duplicate_execution reminder_id=gotowebinar-triage-automation

These warnings accumulate with no aggregation, no alerting, and no operator notification.

What Operators Can See Today

• Nothing, unless they manually run: grep "reminder_skipped_duplicate_execution" /home/netclaw/.netclaw/logs/daemon-*.log | wc -l
• No Slack notifications when a reminder fires but encounters errors
• No dashboard showing reminder execution status
• No /netclaw reminder status command

Why This Matters

1. Business impact: Critical automation (lead triage, ticket routing, customer ops) silently fails. By the time it's discovered, days or weeks of data may be unprocessed.
2. No alerting: There is no system to detect that automation has stopped working. Operators assume reminders are running because they were configured successfully.
3. Manual investigation required: Discovery requires SSH access to the daemon machine and grep — not scalable for any fleet with multiple agents or reminders.

Recommended Features

Short-term

• Add Slack notification when a reminder fires but encounters errors (not just when it processes new data)
• Add a /netclaw reminder status CLI command that shows current execution state for all reminders

Long-term

• Build a "Reminder Health Dashboard" tracking:
  • Last execution time per reminder
  • Success/failure rate
  • Duplicate skip count
  • Total errors per reminder
• Add automatic alerting to Slack/Teams when a reminder skips execution or fails
• Add reminder delivery observation (see Bug: Session-scoped reminders hang 1h when Discord reply fails #1372, Bug: Session-scoped reminders hang 1h when Mattermost reply fails #1373) — currently delivery failures hang for 1 hour with no notification