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

I am seeing the same issue in another private GitHub.com repository.

The workflow is enabled on the default branch, and both workflow_dispatch and push-triggered workflows run successfully. However, GitHub does not create any event=schedule run objects.

Observed timeline:

• Last successful scheduled run: 2026-11-03 04:23 KST / 2026-11-02 19:23 UTC
• Expected run: 2026-11-03 16:07 KST / 07:07 UTC — no run object created
• Recovery schedule: 2026-11-03 16:37 KST / 07:37 UTC — no run object created

Troubleshooting performed:

• Confirmed main is the default branch
• Confirmed the workflow is enabled
• Confirmed valid cron expressions
• Re-saved and modified the cron schedules
• Renamed the workflow file to force a fresh scheduler registration
• Confirmed push-triggered tests succeed
• Confirmed workflow_dispatch succeeds
• Confirmed that no job or runner logs exist because the schedule event itself is not created

The workflow was moved from:
.github/workflows/news.yml

to:
.github/workflows/policy-news.yml

The newly registered workflow also created no scheduled runs.

This appears to be a scheduler event-creation issue rather than a failure inside the workflow job. Is there a way for GitHub staff to check or reset the backend scheduler registration for affected repositories?