GitHub closed #212278 as resolved, but scheduled workflows still don't work in private repositories #213032
Replies: 2 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Update (November 13, 2026): Interestingly, shortly after creating this discussion, my scheduled workflow finally started running. However, it was supposed to run at 04:00 UTC, but the actual run started at approximately 11:50 UTC — almost 8 hours late. This further confirms that the issue is not simply that scheduled workflows fail to run. They can also execute many hours after their expected time. A scheduled workflow that runs almost 8 hours late is not functioning as intended. Could GitHub investigate why scheduled events in private repositories are being delayed or dropped? |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
The discussion #212278 was recently closed with the notification:
"Closed #212278 as resolved."
However, the issue has NOT been resolved.
I am still experiencing the same problem: scheduled GitHub Actions workflows do not run automatically in private repositories.
Manual execution using workflow_dispatch works correctly, but scheduled execution using schedule does not work reliably. Workflows have to be started manually, which defeats the purpose of scheduling.
This is not an isolated configuration issue. Other users have reported the same behavior in the original discussion, including users with private repositories.
The important distinction is that scheduled events appear not to be created at all, rather than jobs starting and subsequently failing on runners.
I would like GitHub to clarify:
What specific fix justified marking discussion #212278 as resolved?
Has the underlying issue with scheduled workflows in private repositories actually been fixed?
Has the fix been deployed to production and verified?
If the issue remains unresolved, why was the original discussion closed as resolved?
Please investigate the actual scheduler behavior rather than suggesting routine YAML or runner configuration checks.
Closing a discussion as resolved should mean that the reported problem has actually been fixed.
Users should not have to manually trigger workflows that are explicitly configured to run automatically.
Related discussion: https://github.com/orgs/community/discussions/212278
All reactions