Replies: 2 comments
-
This is documented behavior for
If you need reliable execution at an exact time, best get dedicated infrastructure instead of relying on Actions. |
Beta Was this translation helpful? Give feedback.
-
Hello, I think this is what happens with one of my Action: the job is skipped even though it is scheduled at 00:35 AM. So I imagine that Github is under high load during a long time starting at midnight: it is not enough to delay it by half an hour or so. I was afraid that there would be something wrong with my schedule, shown below, as the issue happens between the two days (Wednesday and Thursday), but I believe it is a coincidence, and that the issue is the high load at midnight. on:
workflow_dispatch:
schedule:
- cron: '35 18-23 * * 3'
- cron: '35 0-12 * * 4' Edit: I realize the hourly job is not skipped, it is delayed by close to an hour (hence my confusion). |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi everyone, I've been trying to set up a cron job in GitHub Actions to run a workflow every day at midnight. I used the following configuration for the schedule trigger:
However, the job doesn't seem to be running at exactly midnight. Sometimes it runs a few minutes later, and other times it doesn't seem to run at all. I've checked the time zone of my runner and it's set correctly, so I'm not sure what the issue could be.
Has anyone else experienced this problem before? Does anyone have any suggestions for how I can get my cron job to run reliably at midnight?
I also noticed that upgrading to an enterprise account might help with this issue. Does anyone have experience with this?
Thanks in advance for your help.
Beta Was this translation helpful? Give feedback.
All reactions