---
name: routine-health-check
description: Use daily, or when the person asks whether their scheduled tasks are working. Reviews every routine or scheduled task the bot runs, finds runs that failed, stopped, went quiet, ran twice, or started producing empty or stale output, and reports only the problems with a suggested fix for each.
metadata:
  id: routine-health-check
  version: "1.0.0"
  author: BotPlaza
---

# Routine Health Check

## What it does

Watches the watchers. A bot can run a dozen scheduled tasks, such as a morning paper, price alerts, and inbox digests, and one can quietly break: a connector disconnects, a site starts blocking it, or a task posts the same thing every day. This check finds those problems early and tells the person only when something's wrong.

## When to use

- On a daily schedule, or when the person asks "are my routines working?".

## Requires

Access to the bot's own list of routines or scheduled tasks, with their run history or last output.

## Schedule

Default: daily at 6:00 AM, before the morning routines run. It stays silent when everything is healthy.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `quiet_threshold` | 2 missed runs | How many missed runs count as "went quiet". |
| `stale_check` | on | Flags output identical to the last 3 runs. |
| `report_healthy` | weekly | A one-line "all 7 routines healthy" every Monday. |

## Steps

1. **List** every routine with its schedule, its last run, and its result.
2. **Find problems:**
   - failed runs and their errors;
   - missed runs (no run when one was due);
   - duplicate runs;
   - empty, error-filled, or identical output;
   - a disconnected connector that a routine needs.
3. **Diagnose** each problem in one line, for example "the calendar connector needs to sign in again" or "the store blocks automated reads".
4. **Suggest a fix:** reconnect, change the time, pause, or merge duplicates. Apply it only with the person's OK.
5. **Report** only the problems. Stay silent on healthy days, except for the weekly summary.

## Output format

```markdown
**Routine check · {date}:** 2 of 7 need attention
- **Inbox Digest:** failed the last 2 runs. Email connector needs you to sign in again.
- **Price Drop Watcher:** same output 4 days running. One store is blocking reads; drop that item?
```

## Edge cases

- **A routine was paused on purpose:** don't flag it.
- **A one-off reminder that has already run:** suggest deleting it.

## Boundaries

- Never delete or change a routine without the person's OK.
- Never re-authorize a connector on the person's behalf.