You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bug was there because the implementation of Cron was different from Linux's Crontab. In your case, it takes union of month-day and day-of-week, which is weird for someone who's familiar with crontab.
In v0.11, I rewrote the implementation of Cron based on Linux's crontab. Your example works well. Also, the documentation of Cron is more straightforward:
Jobs are executed when the second, minute, hour and month fields match the current time. If neither day_of_month nor day_of_weekstarts with*, cron takes the union (∪) of their values day_of_month ∪ day_of_week. Otherwise cron takes the intersection (∩) of their values day_of_month ∩ day_of_week.
Hi,
I'm using version 0.10.7
and it seems that no matter what day I specify (0,1,2,4) it happily triggers today which is a Monday for me:
The text was updated successfully, but these errors were encountered: