---
title: "Discussion on \"Cron Job Running Twice (or Not at All)? Fix the Job, Not the Schedule\" | Hashnode"
description: "Discussion on \"Cron Job Running Twice (or Not at All)? Fix the Job, Not the Schedule\". Duplicate runs, missed runs and late runs share one root cause. Here's the run-ledger pattern, with SQL and the Laravel, Kubernetes and systemd settings that matter."
url: "https://hashnode.com/posts/cron-job-running-twice-run-ledger/6ae1a0d2af08d0350032cd3e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cron Job Running Twice (or Not at All)? Fix the Job, Not the Schedule](https://simplyexplained.hashnode.dev/cron-job-running-twice-run-ledger?utm_source=hashnode&utm_medium=feed)

Duplicate runs, missed runs and late runs share one root cause. Here's the run-ledger pattern, with SQL and the Laravel, Kubernetes and systemd settings that matter.

Oct 28 · 10 min read · simplyexplained.hashnode.dev  
Read the article

-   [#cron](https://hashnode.com/tag/cron)
-   [#backend](https://hashnode.com/tag/backend)
-   [#laravel](https://hashnode.com/tag/laravel)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#databases](https://hashnode.com/tag/databases)

## Written by

[Adam Jaber](https://hashnode.com/@adamjaber)

@adamjaber · Delhi, India

  
[View profile](https://hashnode.com/@adamjaber)

Senior engineer. How AI and software work — and where they quietly break.

I'm a senior software engineer. I write Simply Explained, a plain-English breakdown of how AI and software actually work, and the quiet ways they break: AI fixes that hide bugs, agents that pick the wrong tool, health checks that take down healthy servers. One symptom, one analogy, one fix per piece. New here? Start with the pinned Start Here guide, or get one breakdown a week by email.

## Responses 1

Markdown supported · ⌘↵ to post

[Kamran Khan](https://hashnode.com/@kamrankhandev)

[Oct 30](https://hashnode.com/posts/cron-job-running-twice-run-ledger/6ae1a0d2af08d0350032cd3e/comment/6ae49886de402a02763fa27a)

The three questions are the right frame, especially the second one. In my experience the double run is rarely a scheduler bug, it is two workers both thinking they own the job. I now treat every scheduled job as if it will run twice, so I give it a unique key or a lock and make the work safe to repeat. The other change that helped me most was alerting when the expected run is missing, not just when a run fails, because a silent miss is the one nobody notices until a customer does.
