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.

  • Ctrl Zee@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    8 hours ago

    Loved the replies. Once it’s over (that’s the hard part), everyone has a funny story to tell!

    Mine was a race condition in an outsourced core system that showed up about six months after release, only when enough transactions hit at the same moment. The contact centre was on fire, with people calling non-stop.

    Same lesson as yours: when something fails only sometimes, stop staring at the code and look at what else is running at that moment.