Replies: 3 comments 1 reply
|
💬 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. ⭐ |
|
From what you've posted, the config side checks out:
That points at schedule events not being created at all, which is something only GitHub can see. You're not the only one this week:
The few remaining repo/account-side things that can stop a schedule (from the
If all three are clear and you still get zero schedule runs after a few hours, it's the scheduler. Workaround that doesn't depend on the scheduler: call curl -sS -X POST \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/vnd.github+json" \
https://api.github.com/repos/OWNER/REPO/actions/workflows/WORKFLOW_FILE.yml/dispatches \
-d '{"ref":"main"}'
Escalation: open a ticket at https://support.github.com (Actions). Community posts can't reach the scheduler internals. Include:
You can keep the repo name private there, which you can't do here. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
Scheduled workflows are not triggering in a private organization repository, while manual
workflow_dispatchruns succeed.Evidence collected on November 17, 2026:
main, and the workflow file is committed there.active.event=schedulereturnstotal_count: 0.The original schedule was committed at 09:34 UTC:
At 11:11 UTC, I tried the equivalent expression
"17,47 0-23 * * *". No scheduled runs appeared afterward.I also created a separate minimal probe on the default branch:
The probe also showed zero runs when checked at 12:08 UTC. It has since been disabled to avoid leaving a frequent test schedule running. The main workflow remains enabled.
I understand scheduled events can be delayed or dropped under high load. However, neither workflow has produced any scheduled run during the observation period.
What additional checks could distinguish a repository or organization restriction from a scheduler registration or dispatch problem? Is there an appropriate escalation route for this issue?
I have omitted repository identifiers and private run links because this is a public discussion.
Additional check: The organization's billing overview shows GitHub Free, with $0.20 of $12.00 included Actions Compute usage consumed and $0 billable usage. The usage breakdown shows 34 Linux minutes in total for November 16–17. The included allowance does not appear exhausted.
All reactions