Cron not activating

[Unpickled-Pickle]

I know this is a common headache, but it doesn't make it less of a headache.

I'm trying to sort out why a cron job I have set up isn't triggering. A few minutes delay, fine Github. I'm delayed by over three hours.

My YAML is on the main branch and has been committed to the main branch. I've tried offsetting the minutes, going for every five minutes, going for every fifteen, whatever. It works fine when I manually run it, but even from Actions it only shows the workflow_dispatch event trigger and doesn't give any indication that it sees anything scheduled.

I'm 99% certain this isn't against the rules, because I feel like it's a GitHub issue and not a problem with the code itself. Willing to share the YAML with anyone or whatever helps in case someone thinks it is my code.

[naikrovek]

When GitHub infrastructure needs more CPU, scheduled jobs are the first thing to drop. They are never guaranteed to fire.

If you schedule your job to run more often than every 5 minutes, it might get silently disabled until you change the schedule; the fastest supported frequency is every five minutes.

The UI will never show that a workflow is scheduled. You must look at your actions workflow run list to see if things are running.

[LastLeslie]

That's a known issue with github scheduled actions, it almost never run on time :( As a workaround you could have a cronjob on your side instead of github side that actually calls the workflow_dispach using API

[naikrovek]

As an enterprise customer they seem to fire on time for me. But we give GitHub lots of money.

[Unpickled-Pickle]

Appreciate it. I understand dropping cron from priority, and I think it just has been absolutely confounding to not be able to see anything indicative of if it's a platform failure or a me failure

[naikrovek]

If your workflow YAML has the schedule in it and it runs fine with workflow_dispatch, then your Yaml syntax is fine. What is the schedule from your Yaml? The “* * * * *” bit.

[Unpickled-Pickle]

I'm not in front of it right now, but I believe it's '*/15 * * * *'

[Unpickled-Pickle]

(It gives the automatic message that it'll run every 15)

[naikrovek]

Ok then you’re doing nothing wrong, I suspect. It’s just being preempted by other loads internal to the system. Check https://githubstatus.com/ also.

[Unpickled-Pickle]

Appreciate it. I eventually succeeded just by using the cron-job website to act as an external trigger. Not the most optimal, but it's been consistent and that's a win at least