Cron & Task Scheduling (Cron/Systemd Timers/At)

Stop losing your mind when systemd timers silently fail

🧩 The Challenge

You finally moved from crusty old crontabs to systemd timers, thinking you were being fancy, but now you have no idea if the job actually ran or just died quietly in the background. It is infuriating to check a status only to see it finished successfully three days ago when you know the output looks like trash.

💡 The Fix

Start using the systemd-analyze calendar command to verify your intervals actually line up with what you expect before you enable the unit. And learn to check the specific active timer status instead of just grepping process lists.

systemctl list-timers --all
systemd-analyze calendar '*-*-* *:00:00'
systemctl status your-timer-name.timer

⚙️ Why It Works

Running the list-timers command shows you exactly when a task last triggered and, more importantly, how long until the next scheduled run. By validating your calendar syntax with systemd-analyze, you skip the guesswork that usually ends with you waking up at 3 AM because a monthly job didn’t fire on the 31st.

🚀 Pro-Tip: Use systemctl cat to see the full timer configuration without hunting through /lib/systemd/system manually.

Linux Tips & Tricks | © ngelinux.com | 11/15/2026