How to Build an Agentic Cron System That Actually Wakes You Up When Something Breaks

Description and use

An agentic cron monitoring system using Telegram alerts reduces failure detection from weeks to minutes for critical workflows.

Problem

Cron jobs often fail silently, causing delayed discovery of failures such as missing blog posts or stopped services.

Outcome

The system reduces failure detection latency from weeks to minutes, ensuring critical workflows like blog publishing and email processing are immediately alerted.

Workflow

• Define failure modes and severity tiers (1‑3).
• Create watchdog scripts that run at defined intervals (e.g., every 10 min or 30 min).
• In watchdog, check for expected artifacts (blog post file, service logs, git commits).
• If check fails, generate a descriptive message.
• Send alert via Telegram API to either a group (tier 2) or personal channel (tier 3).
• Log non‑critical failures and retry automatically (tier 1).

Evidence

Most cron jobs die quietly. They fail, they silently skip, they run the wrong script — and you find out three weeks later when someone asks why the blog stopped publishing.

Source

The fix is not better monitoring software. It is making your cron jobs agents — things that know when to escape, that can send you a message when the morning's work didn't happen, that distinguish between "nothing to do" and "something went wrong."

Source

This script runs at 10am. If no post from yesterday exists, Amre gets a message before she's finished her first coffee. The failure is visible within minutes, not hours.

Source