53

had this bizarre issue where a backup script ran fine monday through friday but failed every saturday. took me way too long to figure out.

turns out the script was calling an internal API that had rate limiting. during the week, the backup ran at 2am when nobody was using the system. on saturdays, some other batch process kicked off at the same time and ate up all the API quota.

the fix was dead simple — stagger the start time by 30 minutes. but finding the cause? that was a couple hours of my life I'm not getting back.

moral of the story: if your cron job is failing intermittently, check what else runs at the same time. crontab -l only shows YOUR crontab. other users and system crontabs in /etc/cron.d/ might be competing for the same resources.

you are viewing a single comment's thread
view the rest of the comments
[-] elvith@feddit.org 3 points 12 hours ago

We had a pipeline suddenly fail everytime when it ran on its weekly schedule but all manual triggers were OK.

After a few weeks we learned that the Linux admins had moved the weekly patch window of the runners to exactly the time our schedule ran the pipeline and this caused all kinds of unpredictable problems.

We then moved the scheduled time and since then the pipeline runs without a hitch

this post was submitted on 16 Nov 2026
53 points (93.4% liked)

Programming

29290 readers
387 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS