Scheduled workflow is enabled but no workflow runs are created

[bizpick]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

I have a scheduled workflow in a private repository on GitHub Free, but no workflow runs are being created.

The workflow is on the default branch (main) and contains:

on:
schedule:
- cron: '17,47 * * * *'

Relevant details:

• The repository is private, not archived, and not a fork.
• main is the default branch.
• Actions are enabled for the repository.
• The workflow was manually enabled, and the UI displayed:
  Workflow enabled successfully.
• The repository-level enable variable used by the job condition is set to the exact lowercase string true.
• The account currently has unused included Actions minutes.
• Multiple scheduled times have passed since enabling the workflow.
• The Actions workflow-runs API still returns:
  {"total_count":0,"workflow_runs":[]}
• I also checked the run list without filtering by event, and there are still zero runs.
• No manual dispatch or re-run has been performed.
• Local YAML parsing and review found no issue with the schedule definition or job-condition structure, although I understand that local validation does not prove GitHub registered the schedule.

Because there is no workflow run at all, I have not reached the runner/job stage. Therefore I don't think a job-level condition, secret, HTTP request, or application logic explains the absence of run records.

I understand that scheduled workflows can sometimes be delayed or dropped, so I am not assuming this is a confirmed GitHub outage.

Is there a way to determine whether:

1. GitHub has successfully registered the scheduled workflow,
2. an account/repository-level Actions restriction is preventing scheduled events from being created, or
3. there is a workflow validation/scheduling issue that is not visible in the UI?

I would prefer not to manually dispatch the production workflow while diagnosing the missing scheduled events.

Thanks.

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

[ryux1]

Your reasoning about the job-level condition is correct: an if: can skip a job, but it cannot explain why no workflow-run object exists at all.

There is no public API for the scheduler's internal registration or its next planned run. The workflow endpoint exposes state, while the runs endpoint exposes only runs that were actually created. I would collect these three read-only checks:

gh api repos/OWNER/REPO/actions/workflows/FILE.yml \
  --jq '{id, path, state}'

gh api 'repos/OWNER/REPO/contents/.github/workflows/FILE.yml?ref=main' \
  --jq '{path, sha}'

gh api repos/OWNER/REPO/actions/permissions \
  --jq '{enabled, allowed_actions}'

You want state: active, the expected workflow blob on the current default branch, and repository Actions enabled. Also compare that blob's commit time with the missed schedule windows; scheduled runs use the latest commit on the default branch.

GitHub documents that schedules can be delayed and, under sufficiently high load, dropped. It specifically calls out the start of the hour. Your 17,47 minutes already avoid that hot spot, so multiple missed windows with total_count: 0 are less consistent with ordinary top-of-hour delay, though still not proof of an outage.

If you want to separate a workflow-specific problem from a repository/account problem without dispatching production, add a temporary, inert schedule-only workflow on main whose sole step prints date -u. Give it different off-hour minutes and no secrets or production conditions. If that also creates no run objects, remove it and include both workflow IDs, states, blob SHAs, expected UTC windows, and empty run-list responses in a GitHub Support ticket. Only GitHub can inspect the backend scheduler state that the APIs do not expose.

Relevant GitHub documentation:

• Events that trigger workflows: schedule
• REST API endpoints for workflows
• REST API endpoint for repository Actions permissions

[Nackers8]

Thanks. I followed your suggested isolation test and have reproduced the issue in a separate private repository.
My account is Nackers8.
I have two private repositories:
Nackers8/TrendTrackerPro
Nackers8/SchedulerTest
TrendTrackerPro has a production workflow where workflow_dispatch works successfully, but scheduled events are not creating workflow runs.
I then created SchedulerTest as a separate repository with a minimal workflow containing only schedule, workflow_dispatch, and a single echo step. It is on the default main branch with no secrets or production conditions.
The test schedule was 30 4 * * 1-5 (04:30 UTC / 12:30 PM Perth) on 7 September 2026. The scheduled time passed and the workflow still showed 0 workflow runs.
Actions are enabled and my Actions usage is not exhausted.
So the fresh inert workflow in a separate private repository also fails to create a run. This makes a workflow-specific configuration issue much less likely.
Unfortunately I don't have access to the scheduler registration state or next planned run, so I believe this now needs GitHub to inspect the backend scheduler state.
Hopefully this additional reproduction helps confirm the issue.

[Rohith-Itagi7]

One thing I would check is whether GitHub is actually registering the schedule event, since scheduled workflows only run from the default branch.

GitHub also notes that scheduled events can be delayed or even dropped during periods of high Actions load, especially around the start of an hour. Since 17 and 47 are away from the hour, that makes a persistent zero-run state more worth investigating.

I’d verify the workflow is enabled and present on main, then try a temporary schedule such as 23 * * * * to rule out scheduling/load behavior.
https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

[Nackers8]

Thanks. I followed your suggested isolation testing, and we now have some interesting results.
I have three scheduled workflows running on the same private repository, Nackers8/TrendTrackerPro, all on the default main branch:

1. TrendTrackerPro Daily Scan
   Scheduled: 01:30 UTC (9:30 AM Perth)
   Actual scheduled run today: 06:23 UTC (2:23 PM Perth)
   Delay: approximately 4 hours 53 minutes
2. Schedule Diagnostic
   Scheduled: 02:30 UTC (10:30 AM Perth)
   Actual scheduled run today: approximately 07:28 UTC (3:28 PM Perth)
   Delay: approximately 4 hours 58 minutes
3. Fresh Scheduler Test
   Scheduled: 04:00 UTC (12:00 PM Perth)
   Actual scheduled run today: approximately 08:50 UTC (4:50 PM Perth)
   Delay: approximately 4 hours 50 minutes
   The Fresh Scheduler Test is an inert workflow with only a scheduled trigger, workflow_dispatch and a single echo step.
   All three workflows are being created as genuine schedule events and are completing successfully once they start.
   The most interesting part is that the configured schedule times are different, but the delay is consistently around 4 hours 50–58 minutes.
   This seems less consistent with normal Actions load delay, particularly because the workflows are not scheduled at the top of the hour.
   This also appears to rule out a TrendTrackerPro-specific workflow problem. It looks more like the scheduled event itself is being dispatched several hours after the configured cron time.
   If useful, I can provide the workflow IDs, run IDs, commit SHAs and screenshots.
   Has anyone else seen a consistent ~5-hour delay like this with scheduled workflows on private repositories?