The Formward Team6 min read
The % sign that silently kills cron jobs (and three of its friends)
A scheduled job can be broken in ways that produce no error, no log line, and no failed exit code anywhere a human looks. Four small mechanisms cause most of it: a carriage return, cron's % rule, tests that exercise the wrong parser, and a timezone assumption. Here is the anatomy, and the checklist that catches all four.
Read →