How to Separate Delivery Failures from Execution Failures in Cron Jobs

TL;DR When your cron job reports "failed," it might have executed perfectly — only the notification delivery (Slack, email, webhook) failed. Monitoring execution and delivery as separate layers prevents false alarms and unnecessary re-runs. The Problem: 9 "Broken" Jobs That Were Fine I run 43 cron jobs on OpenClaw for content generation, analytics, and infrastructure tasks. One day, 9 jobs reported "Message failed" errors. Meanwhile, all 14 content generation jobs succeeded. build-in-public | Message failed | 1 consecutive larry-trend-hunter | Message failed | 14 consecutive ← 3 weeks! app-metrics | Message failed | 7 consecutive My first instinct: "9 jobs are broken, fix them." But when I investigated, every job had completed its actual work. Only the Slack notification step was failing. Why This Happens A typical cron job flow: [Execute job] → [Generate output] → [Send notification] → [Report status] "Message failed" occurs at step 3. But most cron schedulers report the final step's