Replies: 5 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. ⭐ |
|
Hi, Given that There are three key factors at play here, especially with the workflow registered on November 11: 1. Scheduler database desync from the Nov 11 Actions incidentThe November 11 GitHub Actions backend incident disrupted cron job registration for newly added workflow schedules. When this occurs, simply editing the file or toggling the workflow disable/enable switch does not always purge the corrupted scheduler entry from the internal Actions scheduler database. The proven workaround to force a completely fresh scheduler registration:
2. Organization billing & private repository spending limitsPrivate repositories draw from the organization's paid/included Actions minute pool:
3. Actor 2FA / Session EnforcementWhen a cron job triggers, GitHub Actions evaluates the repository permissions and security posture of the user account who last committed the workflow file:
Renaming the file usually unblocks this immediately. |
This comment was marked as spam.
This comment was marked as spam.
|
We saw a similar issue in a private repository on November 14, 2026. Our workflow is enabled on the default branch. No scheduled runs appeared for 03:00, 03:27, or 04:43 UTC, while a manually initiated run succeeded later that day. Scheduled runs on November 13 did appear, several hours later than expected. Has anyone found a way to determine whether the missing events were delayed or dropped? |
|
@MrBergx GitHub's docs say schedule events can be delayed under heavy load, and some can be dropped. Your setup already matches the docs: default branch, off-peak minutes. One question: your diagnostic cron is 45 9-23 * * * (minute 45), but you checked :55. Which minute was it when you tested? If it's still empty, GitHub Support is the next step. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
Repository: Repository: a private, organization-owned repository. Workflow file on the default branch main.
Since the schedule trigger was first added (merged 2026-11-11 16:44 UTC), not a single scheduled run has ever started — the workflow's run list contains only workflow_dispatch events, which trigger and execute correctly every time. The workflow is enabled, the repository has daily activity, and the Actions UI shows no warning.
Current cron expressions on main: "17 7 * * *", "17 8 * * *", and a temporary diagnostic line "45 9-23 * * *".
What we have tried, without effect:
A second workflow in the repo (pull_request-triggered) runs normally, as does workflow_dispatch on this workflow — the issue is specific to the schedule trigger.
Could you check why the scheduler never fires for this repository/workflow?
All reactions