GitHub Actions scheduled workflows never trigger - reproduced in two independent private repositories #212867
Replies: 3 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
This comment was marked as low quality.
This comment was marked as low quality.
|
I’m experiencing the same issue with a private repository. I’ve confirmed that:
I’ve also checked the Actions runs API directly. It currently shows only manual executions and no scheduled runs. This has persisted despite changing the cron expressions and committing the changes to the default branch. I’m on GitHub Free, so I don’t appear to have access to direct technical support tickets. Is there a way for GitHub staff to investigate this through this discussion? I’m particularly interested in whether scheduled events are being generated and delivered for my repository. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
Hello GitHub Team,
I am reporting an issue with GitHub Actions scheduled workflows that has persisted since early November 2026.
Problem description
GitHub Actions workflows triggered by schedule do not execute at all. However, the same workflows run successfully when triggered manually using workflow_dispatch or by a push event.
The issue has been reproduced in two completely independent private repositories.
What I have tested
Verified that main is the default branch.
Confirmed that the workflows are enabled and their state is active using the GitHub REST API.
Tested multiple cron expressions, including */5 * * * *.
Removed the timezone configuration to rule out timezone-related issues.
Created new workflow files with different names.
Created a completely new private repository containing only a minimal GitHub Actions workflow.
Confirmed that manual executions and push-triggered executions work correctly.
Checked workflow run history through the GitHub REST API.
API results
Both repositories return:
{
"runs": [],
"total_count": 0
}
when querying runs with event=schedule.
Minimal reproduction
name: Schedule Test
on:
workflow_dispatch:
push:
schedule:
- cron: "*/5 * * * *"
jobs:
test:
runs-on: ubuntu-latest
steps:
- run: date -u
This workflow runs successfully when triggered manually or through a push, but scheduled runs are never created.
Expected behavior
Scheduled workflows should automatically trigger according to their cron expressions.
Actual behavior
No scheduled workflow runs are created. There are no failed jobs or skipped jobs because the scheduled workflow is never triggered.
Request for investigation
Could GitHub staff investigate whether there is an issue with the GitHub Actions scheduling infrastructure, scheduler registration, or the account associated with scheduled workflow execution?
I have found other users reporting similar behavior during November 2026.
Is this a known issue? Is there an official workaround or an estimated resolution date?
I can provide the affected repository URLs and workflow IDs privately if required.
Thank you for your assistance.
All reactions