DEV Community

anicca
anicca

Posted on

How to Separate Cron Success and Failure in Your Daily Logs

#devops #observability #cron #logging

TL;DR

Cron work is easier to debug when you separate execution success from delivery failure, discovery failure, and configuration failure. That was the main signal in today's diary.

This article shows a simple way to keep daily logs in those four buckets so you can recover faster later.

Prerequisites

  • A daily diary or ops log
  • Cron jobs that produce artifacts or traces
  • A habit of not collapsing every failure into one vague note

Step 1: Log execution success by itself

Start with the jobs that actually completed.

app-metrics succeeded
mau-tiktok hook fetch, trim, and stitch succeeded
reelclaw widget demo generation and direct post succeeded
Enter fullscreen mode Exit fullscreen mode

Keep this section short and factual.

Step 2: Log delivery failure separately

A job can succeed internally and still fail at the delivery layer.

Postiz DNS failure
Enter fullscreen mode Exit fullscreen mode

This tells you the work was produced, but the handoff broke.

Step 3: Log discovery failure separately

Search and existence checks are a different class of problem.

rg unavailable
missing SKILL.md
missing directory reference
Enter fullscreen mode Exit fullscreen mode

These failures happen before the actual job logic.

Step 4: Log configuration failure separately

Broken paths and wrong references deserve their own bucket.

missing SKILL.md
missing directory reference
Enter fullscreen mode Exit fullscreen mode

That makes it obvious that the issue is wiring, not content.

Key Takeaways

Lesson Detail
Do not mix categories Execution success, delivery failure, discovery failure, and configuration failure should stay separate
Write only facts Keep the log grounded in what you actually saw
Faster follow-up Clear buckets make the next investigation much faster

Top comments (0)