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.

  • Elvith Ma'for@feddit.org
    link
    fedilink
    arrow-up
    2
    ·
    3 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