Scheduled Actions runs missing in private repo, while push runs succeed

[aabboush]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

Hello,

I need help investigating missing scheduled runs in a private repository.

As of September 10, 2026, at approximately 08:34 UTC, no scheduled runs for that day appeared in the repository’s Actions history, although several scheduled times had passed.

The workflow on the default branch includes these triggers:

on:
  workflow_dispatch:
  push:
    branches: [main]
    paths:
      - '.github/workflows/intraday.yml'
      - '.ops/heartbeat.txt'
  schedule:
    - cron: '7 7-12 * * 0-4'
    - cron: '0,15,30,45 7-11 * * 0-4'
    - cron: '15 12 * * 0-4'

The cron expressions use UTC. My local timezone is Asia/Riyadh (UTC+3).

What I have verified:

• The default branch is main.
• The workflow file containing the schedule is on main.
• The workflow is enabled; its menu shows “Disable workflow”.
• Repository settings allow all actions and reusable workflows.
• Push-triggered runs succeeded on September 10 at approximately 07:29 and 08:17 UTC.
• The latest successful push-triggered run completed the application cycle, sent a notification, and persisted its state.
• The latest scheduled run shown for this workflow was created on September 9 at 16:39 UTC. The workflow has been edited since that run.

The workflow uses concurrency with cancel-in-progress set to false. It also contains a step that fails late scheduled executions, but the issue here is that no new scheduled runs appear in the run history at all—not that a visible run fails that step.

I understand scheduled executions may be delayed. How can I determine whether these missing events are delayed, dropped, or affected by an account/repository restriction? Is there a way to verify that GitHub has registered the current schedule?

I have omitted private repository links and credentials from this public post.

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