# When a Reddit monitor goes quiet

Zero NEW posts does not mean the collector is broken. Check collection health before keyword filters, deduplication, or destination mapping.

| What you see | What it means | What to check |
|---|---|---|
| Recent successful run; expected sources have fresh successful checks, zero failures and uninterrupted coverage; zero NEW rows | Healthy silence: posts may already be seen or filtered out | Keep the same monitor name and scope; no outage alert is needed |
| Run SUCCEEDED, but a source has failures or missing health | The process finished, but source collection failed or is unknown | Inspect that run's SUMMARY and ERRORS; handle each source separately |
| A completed run reports possibleGap or coverageInterrupted, then the next run clears it | The Actor caught up through its continuation; an initial item-limited backfill may do this | The optional watchdog keeps it pending and drops it silently when it clears |
| Coverage stays interrupted on the next distinct successful run | A persistent gap needs attention | Inspect continuation/retry guidance; for an item-limit stop, raise maxItems or run more often |
| Last successful source check is old while other sources keep working | A stale source, not necessarily an empty community | Compare `lastSuccessfulCheckAt`, `lastAttemptAt`, `consecutiveFailures` and `coverageInterrupted` |
| No recent run started | Scheduler, credentials, quota or upstream workflow may have stopped | Check the collector task's run history and its scheduler; use an independent watchdog |
| Latest run is still RUNNING within the expected runtime plus grace | The collector may simply be slow | Wait or inspect that same run; do not start another run blindly |
| Apify metadata or SUMMARY cannot be read | Health is unknown | Check API availability, credential permissions and record retention; never convert an API failure into “no new posts” |

For an hourly collector, a useful initial missed-run threshold is **two hours plus 15 minutes of grace**. A checker running every five minutes detects the breach on its next successful check; this is not an exact delivery-time guarantee. Tune the interval and expected runtime for your task. A first check with no run history waits the threshold from watchdog initialization rather than immediately declaring an outage.

## Optional independent n8n watchdog

The [inactive watchdog template](https://api.apify.com/v2/key-value-stores/9ZywSAVVA8tMMdMQC/records/reddit-collection-watchdog-v1-n8n.json) checks an existing dedicated Apify task. It does not run the collector. It uses the exact completed run's `MONITOR_STATE` and `SUMMARY`, checks the expected monitor name and sources, and queues incident/recovery events in a persistent n8n Data Table. [Setup and limitations](https://api.apify.com/v2/key-value-stores/9ZywSAVVA8tMMdMQC/records/reddit-collection-watchdog-v1-setup.md).

The collector already reports source health inside its executions. This optional checker covers the gap when those executions stop starting. A separate workflow on the same n8n host can detect a disabled collector workflow, but **cannot alert when that entire host is down**. Use another host/service for that failure domain, and an external uptime/dead-man check for the watchdog itself.

Only successful health evidence clears a source incident. API outages, missing records and collector crashes leave existing source incidents open. Reminders are off by default. Notification retries preserve event IDs; a receiver with durable per-event receipts prevents replayed notifications after an ambiguous delivery. A plain Slack webhook alone cannot guarantee this.

Coverage-gap alerts default to `gapAlertAfterRuns: 2`. The same completed run ID seen by several checker executions counts once. Pending gaps are tracked per global/source key and clear without notifications if the next successful observation is clean. Use `1` for immediate gap alerts. Failures, missing/stale sources and failed runs still alert immediately; this grace applies only to coverage flags. The checker can only count completed successful runs it observes, not intermediate runs skipped between checks.

Do not warn just because a feed is naturally quiet or because no rows passed a filter. This version deliberately does not infer raw source inactivity from NEW counts and does not include automatic “unexpected silence” warnings.

## Before enabling

1. Choose one stable monitor scope and a dedicated collector task. Copy the exact expected source descriptor objects from its known-good SUMMARY; do not point at the Actor's mixed run history.
2. Read the template setup. Test healthy zero-result, failure and recovery fixtures first, then your read-only metadata connection and notification destination.
3. Keep one state row per watchdog key. The template's conditional lease protects overlapping checks of that row; do not create duplicate rows or separate state stores for the same key.
4. Keep your existing collector schedule. Enable only the watchdog's independent checking schedule after review; it makes no collection POST requests.

These files are a local optional integration, not a deployed service. No Actor runtime changes, public template replacements or live schedule changes are required by this guide.
