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. ⭐ |
|
Your configuration is verifiably correct — trigger on the default branch, valid cron, workflow enabled, minutes available, repo unarchived and active. When dispatch works and the schedule produces zero runs (not delayed ones — none at all, no queued/failed/skipped records), the remaining explanations are all on the platform side:
What I'd do concretely:
|
This issue is caused by a known limitation with GitHub Actions scheduled workflows in private repositories on GitHub Free, combined with scheduling delays. Here is the explanation for why this happens and how to diagnose it:
Commit History on Default Branch: GitHub's schedule parser only registers cron jobs when the workflow file is present on the default branch (main). If the change was pushed via a pull request or side branch, the schedule will not trigger until merged. Audit Logs (For Enterprise/Paid Accounts): If you have access to Audit Logs, search for workflows.update to confirm the default branch update was indexed properly.
Trigger an Activity: Push a commit or dispatch a manual run on the main branch. This forces GitHub's cron parser to re-evaluate the .github/workflows/ directory. Use an External Cron Trigger: If hourly precision is required for a private repo, set up a free external cron service (like Cron-job.org or GitHub Actions repository_dispatch via a webhook) to trigger the workflow reliably using the REST API. If this response helps answer your question, please mark it as the accepted answer! |
|
This issue is caused by a known limitation with GitHub Actions scheduled workflows in private repositories on GitHub Free, combined with scheduling delays. Here is the explanation for why this happens and how to diagnose it:
Commit History on Default Branch: GitHub's schedule parser only registers cron jobs when the workflow file is present on the default branch (main). If the change was pushed via a pull request or side branch, the schedule will not trigger until merged. Audit Logs (For Enterprise/Paid Accounts): If you have access to Audit Logs, search for workflows.update to confirm the default branch update was indexed properly.
Trigger an Activity: Push a commit or dispatch a manual run on the main branch. This forces GitHub's cron parser to re-evaluate the .github/workflows/ directory. Use an External Cron Trigger: If hourly precision is required for a private repo, set up a free external cron service (like Cron-job.org or GitHub Actions repository_dispatch via a webhook) to trigger the workflow reliably using the REST API. If this response helps answer your question, please mark it as the accepted answer! |
|
Your cron is already off the top of the hour, so the usual fix doesn't apply here. Whatever the cause turns out to be, it helps to stop finding out from the Actions tab: add a last step that pings an external heartbeat URL on success, and alert when no ping arrives within the hour plus some slack. A schedule that never fires, or fires hours late, then reaches you within the hour. Healthchecks.io and Dead Man's Snitch both work this way. I built LastPing for this (free for individuals): it alerts by email, Slack, Discord or webhook when a run never starts or stalls. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Workflow Configuration
Discussion Details
Hourly schedule creates no runs, while workflow_dispatch succeeds
I have a private repository on GitHub Free. Its default branch is main. A workflow that previously completed successfully through workflow_dispatch was updated on 2026-10-16 at 03:51 UTC to add this trigger:
This is a trigger excerpt, not a complete workflow. The existing job remains unchanged: ubuntu-latest, timeout-minutes 2, permissions {}, a main-branch guard, and a concurrency group with cancel-in-progress false. It has no checkout or third-party actions.
At 06:48 UTC on 2026-10-16, the Actions UI and REST workflow-runs endpoint still show only the earlier successful workflow_dispatch run. No schedule run was created for the nominal 04:17, 05:17 or 06:17 UTC occurrences. There is no queued, failed or skipped run and no run-level error to inspect.
Checks already performed:
I understand scheduled workflows can be delayed or dropped under load. Is there a documented way to determine whether this new schedule was registered, or identify an account/repository scheduling restriction when no run is created?
Repository URLs, account identifiers, run IDs, application endpoints and credentials are intentionally omitted from this public draft.
All reactions