Jobs don't run when scheduled

[Stian Lind Petlund]

Hi all,

Not sure if there are any active members in this group, but I'm trying anyways :)

We've set up a bunch of cron jobs as simple GET requests to some public cron endpoints. Some of our jobs run miss schedule, and run too late.

The weird thing is that it seems like less frequently scheduled jobs (e.g once a day or once a week) more often miss their schedule and run late.

Example: We have a job scheduled for 11 PM on Fridays, and this Friday it ran 12:16 AM (1 hr and 16 mins too late).

Our endpoints respond with 200 immediately, so this isn't a timeout issue or similar. From the logs I can see that we get AttemptStarted and AttemptFinished events at 12:16, so this have to be a problem with the scheduling itself.

Another weird thing is that on Fridays we also have a job scheduled for 11:30 PM, this job also ran 12:16 AM. So it seems to be the case that these two jobs are both prioritized at the same time Friday night.

We also have scheduled jobs that run e.g every 5th minute. These jobs run on time, every single time. Also when the 11 PM and 11.30PM jobs doesn't start - these more frequent jobs run fine.

The only logical explanation I can think of is that cloud scheduler keeps more frequent jobs "warm" so they run on time, and less frequent jobs may miss their schedule because they aren't prioritized or something?

Anyone had similar issues?

[Marcus Ebert]

This doesn't seem to be an issue with the cloudscheduler project this group was made for. Unfortunately, Google decided to call one of their projects also cloud-scheduler later one. Please see here for details: https://groups.google.com/g/cloudscheduler/c/l_X_BS1pUe0