Why Your Scheduled GitHub Actions Workflow Runs Late (or Stops Running Entirely)
You set up a workflow to run every morning. It worked for a week, then two weeks. Then one day you check the Actions tab and see the last run was a month ago. No error. No email. It just stopped. If you use GitHub Actions for small automations like reports, checks or posts, this can happen to you. The scheduler isn't broken. It just works differently from what most people expect. "Every day at…
GitHub Actions workflows can stop running unexpectedly. This can happen even if the schedule looks correct. It's not the scheduler's fault; it just works differently from what most people expect. The source says scheduled runs can be delayed when many workflows run simultaneously, with the busiest time being the start of every hour.
To avoid this, try changing the schedule to a less busy time, like 17:09 instead of 09:00. Another issue is the 60-day quiet period for public repositories. GitHub automatically disables scheduled workflows after 60 days without any activity. To fix this, re-enable the workflow in the Actions tab after any new repository activity.
Additionally, scheduled workflows only run from the default branch and not feature branches. If your workflow exists only in a forked repository, it won't run until you enable it there. The source also notes that cron times are in UTC by default, so times like 09:00 may not match your local time. If a workflow is removed from the repository due to the person who last edited it being removed, the scheduled workflow can also be disabled.
Lastly, a workflow that runs too frequently, faster than every 5 minutes, won't work. The source advises picking odd minutes, making the job forgiving by ensuring the next run catches up if it's late or skipped, and watching for the absence of a run by adding a small "I finished" ping to a monitoring service. This way, if a workflow stops, you'll be alerted immediately.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
