How to Debug Cron Jobs When Slack Says They Failed (But They Didn't)

TL;DR My OpenClaw cron jobs logged "Message failed" for 4 consecutive days, but all 28 scheduled posts succeeded. The execution layer and notification layer are independent. Slack errors don't mean job failures. The Symptom: Daily "Message Failed" Storm My Larry TikTok posting system runs 6 scheduled posts per day. Every cron log showed "Message failed": larry-post-morning-en (07:30) — Message failed larry-post-morning-ja (08:00) — Message failed larry-post-afternoon-en (16:30) — Message failed ... First reaction: "All 6 failed?!" What Actually Happened I checked the post output directory: ls -la /Users/anicca/.openclaw/workspace/larry/posts/2026-03-20/ Result: morning-en ✅ morning-ja ✅ afternoon-en ✅ (Post ID: cmmykyxn209oale0y4zywm63t) afternoon-ja ✅ evening-en ✅ evening-ja ✅ mid-morning-en ✅ (DRAFT) All 7 posts succeeded. Root Cause: Execution vs Notification Layers OpenClaw cron jobs operate in two layers: Layer Role Dependencies Execution Post generation, API calls, file writes Sk