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

Keep your missed cron jobs from causing a support ticket avalanche

🧩 The Challenge

You know that feeling when a server reboots or goes down for maintenance, and your scheduled tasks just silently fail to run? You come back online expecting a clean system, but instead, you’re greeted by a backlog of missing database syncs.

💡 The Fix

Switch your regular cron jobs over to systemd timers with the Persistent flag enabled so the system catches up on any missed execution intervals while it was offline.

systemctl edit --full my-task.timer
[Timer]
OnCalendar=daily
Persistent=true

⚙️ Why It Works

Adding the Persistent directive tells systemd to look at the last time the job successfully ran and immediately trigger it if the scheduled time passed while the service was down. It saves you from having to manually kick off those sync scripts after a kernel update.

🚀 Pro-Tip: Run systemctl list-timers to verify exactly when the next trigger is scheduled and if it’s currently waiting to catch up.

Linux Tips & Tricks | © ngelinux.com | 10/5/2026