Scheduled workflow never creates runs, but workflow_dispatch works #210463
Replies: 2 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. ⭐ |
|
Taking your checks as given (default branch, active workflow, enabled Actions, unarchived, valid cron — On the integration question: no. The actor that pushed the commit carrying the Why zero runs then. With dispatch working and the schedule producing no run records at all (not even skipped/failed), the standard causes are exhausted and what remains is platform-side:
Practical path: double-check the API view ( One last note since the runs will eventually matter more than the trigger: your three dispatch runs failed or were cancelled — the schedule will faithfully reproduce those failures, so it's worth a green dispatch run before the scheduled ones start. |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
My scheduled GitHub Actions workflow never creates runs, while workflow_dispatch successfully creates manual runs.
Repository: private
Workflow: ALERTAS hourly surveillance
Workflow ID: 385747417
Default branch: main
As of October 16, 2026 at 13:54 UTC:
Current configuration:
This configuration reached main at approximately 10:38 UTC today. No scheduled runs appeared for 11:07, 12:07 or 13:07 UTC.
Disabling and re-enabling the workflow through my account did not resolve the issue.
Cron changes were committed through the v0 integration. Could the schedule’s associated actor affect eligibility? We have no evidence that the integration caused the problem.
What should we check next to determine why scheduled runs are not being created? Our account does not include direct technical support.
All reactions