Writing
Blog
Scheduled jobs rarely fail loudly. They run hours late, run twice, or stop without a word. These posts show how that happens in cron, systemd timers, Kubernetes CronJobs, GitHub Actions and in-app schedulers, and how to notice before your users do.
Start here
- Why Your GitHub Actions Scheduled Workflows Run Hours LateGitHub Actions treats cron schedules as best-effort. In 2026 the delays are getting worse, with jobs firing hours late and some dropped entirely. Here is why, and how to catch it.
- Preventing Duplicate Cron Jobs When You Scale to Multiple ServersWhen your app runs on two or more servers, every cron job in the crontab fires on every machine. This is how to stop duplicate execution without creating a new single point of failure.
- Why APScheduler Silently Stops Running Your Python JobsAPScheduler runs inside your own process, with a one-second misfire grace and an in-memory job store by default. Here is how it silently drops scheduled jobs.
Loading posts…