Scheduled (cron) workflows not triggering since Aug 26 — multiple repositories affected

[kort0881]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello,

My scheduled GitHub Actions workflows have stopped triggering automatically since approximately August 26–27, 2026.

Manual runs via workflow_dispatch work correctly in all affected repositories. The issue is that no scheduled workflow run is created at all.

Affected repositories and workflows:

1. https://github.com/kort0881/post-bot-telegam/actions
   Workflow: Telegram AI Tech Bot
   Schedule: cron '47 6,9,12,15,18,21 * * *'

2. https://github.com/kort0881/facts-telegram-generator/actions
   Workflow: Generate Facts
   Schedule: cron '15 5,9,13,17,21 * * *'

3. https://github.com/kort0881/No-code-protection/actions
   Workflow: KIBER SOS Autopost
   Schedule: cron '23 6,12,15,18 * * *'

4. https://github.com/kort0881/freecoding/actions
   Workflow: Vibe Articles
   Schedule: cron '38 9,15,21 * * *'

All affected workflows:

• use valid on.schedule cron expressions;
• include workflow_dispatch, and manual runs work;
• are stored on the default branch (main);
• have GitHub Actions permissions enabled.

Could someone confirm whether there is a current platform issue with scheduled GitHub Actions workflows? Please also advise whether there is anything I need to change in my configuration.

Thank you.

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

[kort0881]

I can confirm the same issue.

Since approximately August 26–27, 2026, scheduled GitHub Actions runs are not being created for multiple repositories in my account, while workflow_dispatch runs work normally.

Affected repositories:

• https://github.com/kort0881/post-bot-telegam/actions
• https://github.com/kort0881/facts-telegram-generator/actions
• https://github.com/kort0881/No-code-protection/actions
• https://github.com/kort0881/freecoding/actions

The workflows use different cron minutes (15, 23, 38, and 47), are stored on the default branch, and were working normally before this issue.

My separate bug report:
https://github.com/orgs/community/discussions/206134

Could GitHub staff please confirm whether this is an active incident affecting scheduled workflow triggers?

[Minhal128]

Same symptom is being tracked in #206019, which has a timeline showing the degradation before the drop (39 min late → 3 h 27 → 10 h 41 → no run created at all).

Your crons are useful evidence there, since all four are already on off-peak minutes — that rules out the :00/:30 contention theory being suggested on that thread.

Worth consolidating on one thread; it's currently split across #206019, #206120, #206124 and this one, which probably isn't helping it get noticed.

[kort0881]

Thank you. I have added the details of my four affected repositories and their off-peak cron minutes to #206019 to consolidate the evidence.

[kort0881]

Update on August 30, 2026: the problem is still ongoing.

Additional scheduled times have passed for my affected workflows, including off-peak minutes 15, 23, 38 and 47 UTC. No scheduled workflow runs were created.

Manual workflow_dispatch runs still start and complete normally. This continues to affect multiple repositories under my account.