Replies: 21 comments 10 replies
-
|
💬 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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
I'm facing the same issue |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
I am also facing a similar issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same problem. I can run it manually but it refuses to auto-trigger. I've tried all the things you did and still no luck. I'm starting to think the auto run feature is broken. |
Beta Was this translation helpful? Give feedback.
-
|
having the same issue. Previously working schedules just stopped working |
Beta Was this translation helpful? Give feedback.
-
|
My problems started on Friday. I had no scheduled workflows previously; the ones created on Friday and Saturday either don't run or run intermittently. I create a simple workflow to test the scheduling, which only outputs the time and a dump of its payload. However, I have updated its YAML file several times since it was created, but when I look at the dump of the payload, the parameters are the ones in my original version, not the latest version. |
Beta Was this translation helpful? Give feedback.
-
|
See here. actions/runner#4210 |
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing the same issue: schedule workflows never trigger (even after 24 hours), while workflow_dispatch and push work fine. name: schedule-check
on:
push:
branches:
- main
workflow_dispatch:
schedule:
- cron: "10 * * * *"
jobs:
ping:
runs-on: ubuntu-latest
steps:
- name: Show time in UTC and JST
run: |
echo "UTC: $(date -u '+%Y-%m-%d %H:%M:%S UTC')"
TZ=Asia/Tokyo date '+JST: %Y-%m-%d %H:%M:%S %Z' |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
My newly created repo is not triggering at all either but anything that has triggered before is still working |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
Based on the pattern reported here and the referenced issue actions/runner#4210, this appears to be a known issue affecting newly created scheduled workflows. Key Findings:The Pattern:
Possible Workarounds:
on:
schedule:
- cron: '*/9 * * * *'
workflow_dispatch: # Manual trigger
push: # Or add a push trigger temporarily
branches: [main]
What to Check: While waiting for GitHub to resolve this:
Note: This seems to be a platform-wide issue that started around January 23-24, 2026. GitHub staff will likely need to investigate and provide an official fix. Would recommend upvoting the referenced issue and monitoring GitHub Status for updates. |
Beta Was this translation helpful? Give feedback.
-
|
Renaming "main" branch to "master" resolved the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Still no luck. |
Beta Was this translation helpful? Give feedback.
-
|
Also tried to rename to master - doesn't work |
Beta Was this translation helpful? Give feedback.
-
|
We were having the same issue. Now the actions started to run again. The only change I made was change the default branch from develop to main, and then back to develop. No idea if this had any relation to them coming back alive or it is just something on github side. |
Beta Was this translation helpful? Give feedback.
-
|
Just got this message from GitHub support, still doesn't work for me - but there is hope!
|
Beta Was this translation helpful? Give feedback.
-
|
👋 Thank you for reporting the issue with scheduled workflows not triggering. We identified a related change from last week that was rolled back today. Any commit pushed to the default branch will resync the impacted scheduled workflows and resolve any scheduling issues you may be experiencing. If you continue to experience issues with syncing schedules, please reply with a comment including the following:
Note: Schedules that run during periods of high load (e.g., midnight UTC) may be delayed or, if load is sufficiently high, potentially dropped. Please see our docs for further information. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if it helps here, but if you’re looking for a safety net for scheduled workflows going silent: I’m building CronPulse (dead-man’s switch monitoring). You ping start/ok, and it alerts if an expected OK never arrives (missed/late/hung). Quickstart: https://cronpulse-empire.fly.dev/docs/quickstart If this is off-topic for this thread, ignore — just sharing in case it’s useful. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Bug
What GitHub Actions topic or product is this about?
Schedule & Cron Jobs
Discussion Details
I have an old-ish free personal account, but new Repos. I've tried Private and Public repos. I can't say they previously worked, because I bever used actions before.
I can trigger either manually. They have never run on schedule. Not once!
They appears in the Workflows sidebar.
Allow all actions and reusable workflows is selected.
I'm the last commiter (the only comitter actually).
As these are new Repos the branch is main/default.
The path is .github/workflows/main.yml
I'm out of ideas.
Here's my test worflow trying the new 1vcpu runner. The private repo used ubuntu-latest
name: Simple Test
on:
schedule:
- cron: '*/9 * * * *' # Runs every 9 minutes
workflow_dispatch:
jobs:
test:
runs-on: ubuntu-slim
steps:
- name: Print Hello
run: echo "Hello! The time is $(date)"
Beta Was this translation helpful? Give feedback.
All reactions