this post was submitted on 16 Nov 2026
56 points (93.8% liked)

Programming

29288 readers
388 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
 

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
[โ€“] ultimaluz@lemmy.world 2 points 6 hours ago

not weekends but I had one that failed on two random days in a month and looked totally fine the rest. it's a scheduled job that reads a couple of sites through a logged in browser on my laptop, and those two days the browser just wasn't connected, so the job ran on time and had nothing to read. the log said "ok, nothing new" which is the worst kind of failure lol. now it uses a browser that keeps its own session and the other one only as fallback, and an empty result gets reported as a failure and not as a quiet day. same lesson as yours I guess, check what else has to be alive at that moment, not only what's running