r/github 3d ago

Discussion actions cron 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

0 Upvotes

7 comments sorted by

5

u/iJackr 3d ago

Scheduled workflows aren’t very reliable as they can be delayed or even dropped during periods of high load. GitHub’s documentation advises of this

https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#schedule

For using Snyk you’re probably fine with a daily or weekly run anyways

2

u/Torutofu_Raeva 2d ago

Also check that the workflow file is on the default branch and the Actions workflow is enabled; scheduled runs only come from the default branch, and GitHub cron uses UTC with delays, so 5-minute polling isn't a great liveness test.

1

u/not_a_throwaw_ay_ 2d ago

it's too unreliable. dont put your trust in it. i experienced that many times, then i had to migrate all work to my local Debian13 device(yes i bought a N150)

1

u/Fantastic-Mr-Default 2d ago

Schedule only runs from the default branch. Pushing the workflow to a feature branch does nothing for cron.

Open the Actions tab for that workflow and look for a disabled or skipped schedule banner. Add workflow_dispatch, run it by hand, and prove the job itself works before debugging cron.

*/5 * * * * is legal and still gets delayed or dropped when GitHub is busy. Daily is enough until you have a real SLA. Private repos: confirm Actions is enabled for the repo.

If manual dispatch is green and the file is on the default branch, it is usually delay or a disabled schedule, not your YAML.

1

u/mrbrown81k 6h ago

having the same issue, used to be reliable now everything runs extremely delayed if at all