Scheduled GitHub Actions workflows stopped triggering (schedule events) #212721
Replies: 6 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. ⭐ |
|
Update: Additional GitHub Actions startup failures and internal error Request ID Since opening this discussion, the issue has expanded. Several manual The detailed annotation for run #6175 displays: "An unexpected error has occurred and we've been automatically notified." GitHub provided this Request ID:
This failure occurs at startup, before we can establish that the Python monitor code has executed. Run #6170 completed successfully shortly before these failures, so the behavior appears intermittent. Could GitHub staff please correlate this Request ID with internal Actions service logs and investigate whether this startup failure is related to the missing scheduled ( The scheduled workflow issue remains unresolved as well. Thank you. |
|
Additional update: GitHub-hosted runners are not starting jobs We have identified another issue affecting the same repository. Recent manual workflow_dispatch runs (#6176, #6177 and #6178) remain queued. Run #6178 displays the following messages:
This suggests that GitHub-hosted runner provisioning or assignment may also be affected. We now have evidence of three separate symptoms:
Could GitHub investigate whether these symptoms are related to an Actions infrastructure issue affecting this repository? |
Update — November 12, 2026: Scheduled events are arriving intermittently, with multi-hour gapsFurther investigation confirms that both scheduled workflows are receiving and completing Latest observed scheduled runs (UTC): Workflow | Run ID | Created at | Result -- | -- | -- | -- Monitor Sísmico SGC | 43198397198 | Nov 12, 10:13:12 | Success Prueba de programación GitHub | 43204820882 | Nov 12, 10:56:55 | Success Monitor Sísmico SGC | 43141895251 | Nov 12, 02:30:31 | Success Prueba de programación GitHub | 43146229049 | Nov 12, 03:09:04 | SuccessThe main workflow is configured to run every 10 minutes ( Despite these configurations, the observed gaps between scheduled runs are several hours. Additional checks performed:
This indicates that the problem is not simply a workflow execution failure. Scheduled events are being generated intermittently, but the configured execution frequency is not being maintained. Could GitHub investigate whether scheduled event generation or dispatch is being delayed or dropped for this repository? In particular, is there a way for GitHub staff to inspect the scheduler's expected cron slots and actual dispatch records for workflow IDs This repository supports an operational seismic monitoring system, so reliable scheduled execution is essential. A Windows-based fallback remains active while this issue is investigated. Thank you. |
|
GitHub's Actions docs note that scheduled events can be delayed during high load, especially at the start of the hour, and queued runs can be dropped. Moving the cron away from :00 may reduce that risk, but it wouldn't by itself explain multi-hour gaps across both workflows. Since you already have a Windows fallback, I'd keep that as the reliability path and add an independent heartbeat that alerts when an expected run is missing, recording the expected slot, run creation time, queue/start times, runner type, and request IDs. Your paired workflows and IDs should help GitHub Support correlate expected cron slots with actual dispatch records. |
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 Community,
I need help investigating a persistent issue with scheduled GitHub Actions workflows in my repository.
Repository:
https://github.com/monitoreozjqyML1/Monitor_Sismico_SGC
Problem
Two workflows have stopped receiving scheduled (
schedule) events:monitor_sismico.yml— Workflow ID:349432904prueba_schedule.yml— Workflow ID:413668417Their latest recorded scheduled executions were:
42986260078, November 11, 2026, 08:20:32 UTC.43010848917, November 11, 2026, 11:18:26 UTC.What still works
Manual executions using
workflow_dispatchcontinue to work successfully.Both workflows are active, the repository is enabled, and GitHub Actions permissions are enabled.
Troubleshooting performed
*/10 * * * *to1-59/10 * * * *.None of these actions restored scheduled executions.
Questions
This repository runs an operational seismic monitoring system. We have maintained a Windows-based fallback to prevent interruptions while investigating the issue.
I would appreciate technical guidance before making any further changes.
Thank you.
All reactions