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.


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