GitHub Actions scheduled workflows frequently miss executions

[oferche]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Title: GitHub Actions scheduled workflows frequently miss executions

My private repository, [oferche/concert-alert-agent](https://github.com/oferche/concert-alert-agent), has a scheduled workflow that repeatedly misses executions.

• Workflow: Concert Monitor (fresh schedule)
• File: .github/workflows/concert-monitor.yml on main
• Schedule: 13,43 * * * * (twice hourly), timezone Asia/Jerusalem
• Observed behavior: Many scheduled runs never appear, despite successful runs when triggered. Re-registering the schedule by changing the workflow file has not resolved the problem.
• Example runs: [39731609524](https://github.com/oferche/concert-alert-agent/actions/runs/39731609524) · [39702279602](https://github.com/oferche/concert-alert-agent/actions/runs/39702279602) · [39685397183](https://github.com/oferche/concert-alert-agent/actions/runs/39685397183)

Historical data shows an average of only about 4.7 scheduled runs per day, instead of 48, with gaps lasting over 10 hours.

What could cause this persistent behavior, and how can I diagnose it?
Is there a way to improve reliability while keeping scheduling entirely within GitHub Actions?
I prefer not to rely on external scheduling services or grant them access to my private repository.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐