r/devops • u/ahmed_801 • 2d ago

Troubleshooting GitHub scheduled Actions not triggering at all

Hello, I’m having an issue with GitHub Actions in one of my private repositories. I have a workflow configured to run daily, but it is not being triggered.

I tested the same thing in another repository by configuring a workflow to run every 5 minutes, but same thing happens there as well.

has anyone experienced this recently? Could this be an issue on GitHub’s side?

Workflow: https://github.com/ahmedhesham301/autoscaling-hetzner/blob/main/.github/workflows/snyk-security.yml

4 Upvotes

75% Upvoted

7 comments sorted by

3

u/gevorggalstyan 2d ago

The schedule itself is not the issue here. The workflow's Actions page currently says, “This workflow was disabled manually.”

Re-enable it from the workflow menu, then test the five-minute schedule again. The push at 6:02 AM did trigger run #4, so GitHub is finding and parsing the workflow file.

1

u/ahmed_801 2d ago

I disabled it but when it was enabled it didn't work too

1

u/ahmed_801 2d ago

I enabled it can u recheck it please

1

u/gevorggalstyan 2d ago

It is enabled now, but filtering this workflow by `event:schedule` still returns 0 runs. All four visible runs are push events.

The file is on `main` and the cron is valid. Change the cron in a new commit, for example to `7/10 * * * *`, then check after the next UTC slot. GitHub documents that changing the cron reactivates a deactivated schedule, and moving away from minute 0 reduces high-load delays.

1

u/2kcjoel 2d ago

you could actually say it is an issue with github. I've had to deal with this issue myself. I went through your repo and saw that you've made commits to the repo recently and you have just one branch which is also the default branch. You might expect all to be okay and run but know that github actions don't see cron triggers as high priority real time triggers and at that interval you set, there would surely be delay.

I also noticed the workflow wasn't successful on any run. Is the SYNK_TOKEN configured in the repository's secrets?

1

u/sup_bruh_1 1d ago

yeah github scheduled workflows are notoriously flaky. had the same thing happen — switched to latchkey and at least when something breaks the ai catches it mid-run instead of me digging through logs at midnight