<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Did My Job Run — Blog</title><description>Notes on cron reliability, silent job failures, and keeping scheduled work honest — from the team behind Did My Job Run.</description><link>https://blog.didmyjobrun.com/</link><language>en-us</language><copyright>© 2026 Did My Job Run</copyright><item><title>How to monitor a GitHub Actions scheduled workflow that GitHub turned off</title><link>https://blog.didmyjobrun.com/how-to-monitor-a-github-actions-scheduled-workflow/</link><guid isPermaLink="true">https://blog.didmyjobrun.com/how-to-monitor-a-github-actions-scheduled-workflow/</guid><description>GitHub automatically disables scheduled workflows in public repos after 60 days of no activity. There&apos;s no failed run, no red X, and nothing to alert on.</description><pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate><category>github-actions</category><category>cron</category><category>monitoring</category><author>Did My Job Run</author></item><item><title>How to monitor a systemd timer (list-timers lies to you)</title><link>https://blog.didmyjobrun.com/how-to-monitor-a-systemd-timer/</link><guid isPermaLink="true">https://blog.didmyjobrun.com/how-to-monitor-a-systemd-timer/</guid><description>systemctl list-timers shows your timer as healthy while the job behind it has failed every night for a month. Here&apos;s why, and what to check instead.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate><category>systemd</category><category>cron</category><category>monitoring</category><author>Did My Job Run</author></item><item><title>How to monitor a Kubernetes CronJob without re-running it</title><link>https://blog.didmyjobrun.com/how-to-monitor-a-kubernetes-cronjob/</link><guid isPermaLink="true">https://blog.didmyjobrun.com/how-to-monitor-a-kubernetes-cronjob/</guid><description>Adding heartbeat monitoring to a Kubernetes CronJob has a failure mode plain cron doesn&apos;t: when the ping fails, backoffLimit runs your job again. Here&apos;s the one-line fix.</description><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate><category>kubernetes</category><category>cron</category><category>monitoring</category><author>Did My Job Run</author></item><item><title>Why silent cron failures are the expensive kind</title><link>https://blog.didmyjobrun.com/why-silent-cron-failures-are-the-expensive-kind/</link><guid isPermaLink="true">https://blog.didmyjobrun.com/why-silent-cron-failures-are-the-expensive-kind/</guid><description>A website going down announces itself. A cron job that stops running doesn&apos;t — and that&apos;s exactly why it costs more.</description><pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate><category>cron</category><category>monitoring</category><category>reliability</category><author>Did My Job Run</author></item></channel></rss>