most cron implementations authorize the use of leading zeros to improve readbility (and alignment).
When using a task in the form 01 * * * *, cronexpr complains about bad crontab line: 01 * * * *…
If I remove the leading zero, it works as expected.
Note : I'm using cronexpr through aptible/supercronic
i hope supercronic is not the culprit.
I am having the same issue as well where it errors out when leading 0s is provided in the cron expression. It would be really nice to have the fix available to public.
most cron implementations authorize the use of leading zeros to improve readbility (and alignment). When using a task in the form
01 * * * *
, cronexpr complains aboutbad crontab line: 01 * * * *…
If I remove the leading zero, it works as expected.Note : I'm using cronexpr through aptible/supercronic i hope supercronic is not the culprit.