Scheduled Actions workflow creates no runs; manual and push triggers work

[mozo190]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

A scheduled GitHub Actions workflow in my private repository creates no schedule-triggered runs, while push and workflow_dispatch runs execute successfully.

Repository: mozo190/purchase-pilot-01
Default branch: master
Workflow: .github/workflows/task06-staging-billing-health.yml

On October 3, 2026, no scheduled runs appeared during our observation period from approximately 12:13 to 16:48 UTC. The workflow was already present on the default branch.

Original schedule:

on:
schedule:
- cron: '7,22,37,52 * * * *'
workflow_dispatch:

Troubleshooting performed:

Confirmed that master is the repository's default branch.

Confirmed the workflow file and schedule on the remote master branch.

Confirmed that the workflow is enabled.

Successfully ran workflow_dispatch, including the actual monitoring job.

Successfully ran push-triggered tests.

Disabled and re-enabled the workflow at approximately 13:01 UTC.

Changed the cron expression to '11,26,41,56 * * * *' and merged that change into master at approximately 16:39 UTC. The resulting push run succeeded, but no scheduled run had appeared by 16:48 UTC.

The repository variable used to enable monitoring is set to true. Push runs intentionally skip the monitoring job; manual runs execute it successfully.

The issue is that no schedule-triggered workflow run appears at all, rather than a job failing or being skipped inside a scheduled run.

I understand that scheduled runs can be delayed or dropped under load. What additional checks can determine why this workflow has produced no scheduled runs for several hours, despite successful manual and push runs?

The repository is private. I can share sanitized workflow excerpts and screenshots, but not credentials.

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