💬 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. ⭐

The cron expression itself looks valid. */5 * * * * is supported by GitHub Actions, and the minimum supported schedule interval is 5 minutes.

One thing I'd check first is whether this workflow file is actually on the repository's default branch. Scheduled workflows only run from the default branch, so a workflow that exists only on another branch won't be triggered by schedule.

If it is already on the default branch and several unrelated scheduled workflows stopped running at roughly the same time, that makes a GitHub-side Actions issue much more likely. GitHub also documents that scheduled events can be delayed during periods of high Actions load, and in sufficiently high load some queued jobs can be dropped.

Given that this started on August 27, I'd also check GitHub Status for an Actions incident before changing the workflow itself. The status history shows recent Actions incidents around this period, although the August 27 incident specifically mentions delays to workflows triggered by pull-request events, so I wouldn't assume it explains scheduled workflows without further evidence.

If the workflow is on the default branch and still doesn't appear in the Actions history after several scheduled intervals, I'd include the repository/workflow name, the expected cron times (in UTC), and whether other scheduled workflows are affected when reporting it.