Scheduled workflows never trigger (private, public and org repos); workflow_dispatch works

[onovo1]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

Summary

Since 2026-10-01, no schedule event has created a single workflow run in any of my test repositories. Manual workflow_dispatch runs of the same workflows work normally. Similar reports: #202034, #206028.

Minimal workflow

name: Schedule test
on:
  schedule:
    - cron: '*/5 * * * *'
  workflow_dispatch:
jobs:
  ping:
    runs-on: ubuntu-24.04
    steps:
      - run: echo "Works $(date -u)"

What I tested (2026-10-02, times in UTC)

Repository	Visibility	Who committed the cron	Manual run	Scheduled runs
onovo1/holded-time-reporting	private	me	✅ works	❌ none since 2026-10-01
onovo1/schedule-test	private, then public	me	✅ 13:49	❌ none (cron */5, then 7,37)
QCentroid/schedule-test (org)	private	me, then a different org member	✅ 15:44	❌ none

Already ruled out

• Workflow files are on the default branch (main); gh workflow list --all shows active
• Actions enabled ("Allow all actions"); no org policy restrictions
• Off-peak minutes (:07, :37) and */5, with and without timezone:
• Workflows disabled/re-enabled; cron lines recommitted with verified emails
• Repositories are new (no inactivity); billing within limits
• githubstatus.com shows no Actions incident

Question

Is there a known issue with scheduled workflow delivery right now, or is something blocking schedule events for these accounts/repositories? Any GitHub staff able to check would be much appreciated.

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