Scheduled GitHub Actions are now useless
Scheduled GitHub Actions are experiencing significant delays, rendering them nearly useless. A daily job is now running over 3½ hours late, while an hourly job only executes 30% of the time it is supposed to. These issues raise concerns about the reliability of GitHub's scheduling feature.
- ▪Scheduled GitHub Actions are delayed by over 3½ hours for daily jobs.
- ▪Hourly jobs are only running 30% of the time they are scheduled.
- ▪The delays have led to the conclusion that the scheduling feature is now ineffective.
2 outlets in our directory ran this story, first to last over 5 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ CI/CD avec GitHub Actions — DEV.to (Top)
Hacker News (Newest) files mainly under programming. We currently carry 5,257 of its stories.
Opening excerpt (first ~120 words) tap to expand
Scheduled GitHub Actions are now (in May 2026) so delayed that they are more or less useless. Here I have two graphs I collected from my work GitHub account, one from a daily job we have, and another from a job that runs hourly during office hours. Both jobs run on our own runners. The daily job is now runs more than 3½ hour late per day. And our hourly job is so delayed that it only runs 30% of the times its supposed to run! The time between when a daily job is scheduled to run and when its actually run, in minutes. How many job runs of the hourly job that is skipped each day. With this much delays the scheduling feature is now useless. What is happening at GitHub?! Victor 2026-05-19
Excerpt limited to ~120 words for fair-use compliance. The full article is at Viblo.
Discussion
0 commentsMore from Viblo
