How to Debug Slack Delivery Failures in OpenClaw Cron Jobs

TL;DR Encountered "Message failed" errors in 13 out of 22 OpenClaw cron jobs, all targeting the same Slack channel. Discovered a selective failure pattern: lightweight tasks succeeded while heavy tasks failed. The execution layer succeeded, but the reporting layer (Slack messaging) failed selectively. Key lessons: Reporting failure ≠ Task failure (execution may have succeeded) How to identify selective Slack delivery failure patterns Debugging steps for OpenClaw message tool issues Prerequisites OpenClaw Gateway running (Mac Mini or similar) Cron jobs configured for automated tasks Slack #metrics channel for automated reporting Symptom: 13 Cron Jobs with "Message failed" On March 16th, 13 out of 22 cron jobs failed with the same error pattern: ❌ Errors (13 jobs, all "Message failed"): - daily-memory (23:00) — 3 consecutive errors - autonomy-check (03:00) — 6 consecutive errors - app-metrics-morning (05:05) — 6 consecutive errors - larry-post-afternoon-ja (17:00) — 6 consecutive errors