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. ⭐ |
|
Hi, Missing scheduled runs are a known behavior, and a few specific things are worth checking. Your cron expression itself looks fine ( 1. Scheduled runs are best-effort, not guaranteed GitHub's documentation says that scheduled workflows can be delayed during periods of high load, especially at the start of the hour, and that in some cases runs can be dropped when load is high. Moving from minute 17 to 37 was a good idea, because it avoids the busiest minutes, and you could also try an odd minute like 2. Check the rules that disable or skip schedules
3. Check the workflow file closely on:
schedule:
- cron: '37 * * * *'
workflow_dispatch:
4. Check for GitHub incidents Scheduled-run delays are often tied to incidents. Look at https://www.githubstatus.com history for Actions "delayed" or "degraded" events on the missing days. Several runs created around November 11 were affected by an incident, and other reports describe stuck or missing runs. 5. Make monitoring reliable despite best-effort scheduling Because this is operational monitoring, I wouldn't rely on a single
curl -X POST \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/vnd.github+json" \
https://api.github.com/repos/OWNER/REPO/actions/workflows/FILE.yml/dispatches \
-d '{"ref":"main"}'This avoids the schedule trigger entirely, though a stored token needs minimal permissions (a fine-grained token with Actions write on this repository only). 6. Escalate If you've checked the points above and slots still vanish, contact GitHub Support (https://support.github.com/contact, Actions) with the repository name, the workflow file, the cron expression, the exact UTC times of the missed runs, and the successful run time. State that disabling and re-enabling didn't help. Also, your post is in the "ARC (Actions Runner Controller)" area, which is for self-hosted Kubernetes runners. A scheduled workflow problem fits "Actions" or "Workflow Deployment" better. |
|
3 Useful Websites You Shouldn't Miss! AgeWise: https://agewise-life-lens.lovable.app/ ReelSave: https://reelsave-guide.hatchable.site/ Calculator Hub: https://calculator-net-hub.netlify.app/ |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
Hi GitHub Community!
I'm experiencing an intermittent issue with GitHub Actions scheduled workflows in a private repository.
My workflow runs successfully when triggered manually using
workflow_dispatch, but scheduled executions are frequently missing entirely from the Actions run history.Configuration:
main37 * * * *(UTC)Troubleshooting already performed:
On November 17, 2026, one scheduled run executed successfully around 7:47 a.m. Central. However, subsequent hourly scheduling slots did not produce runs.
I'm aware that GitHub scheduled workflows can be delayed or occasionally dropped, but I'm concerned about the repeated missing executions.
My questions:
This workflow handles operational monitoring, so consistent unattended execution is important.
Thanks in advance for any guidance!
All reactions