3 ms·
Also, scheduled jobs are a joke, they are routinely one to several hours late. I have to use the API to manually trigger jobs (workflow_dispatch) whenever I nee
by oefrha 5y ago
Also, scheduled jobs are a joke, they are routinely one to several hours late. I have to use the API to manually trigger jobs (workflow_dispatch) whenever I need scheduling that is remotely time sensitive.
- 147 5y agoI've heard of issues with scheduled jobs on Github.com but we didn't have any issues so far on GHES.
- chrisfosterelli 5y agoThis was the first thing that came to mind for me too. I don't need it to be exact, sure, but the scheduled jobs are more than an hour off more often than not. Sometimes several hours as you mentioned. Frequently they would also just not run at all! It was so bad I ended up scheduling my cron jobs to run 4 - 5 hours early and just sit there idling until the actual execution time came around haha. Ultimately not running at all started to be a real pain point, I gave up and paid $5 for a monthly box to sit there and run crond to save on the headache.
- seanhandley 5y agoYes their scheduler is woeful. I have a few suspicions that it's intentionally done this way for balancing demand spikes and that jobs scheduled for the top of hour are worst affected.