PatternCron
Weekend mornings
Saturday-and-Sunday-only jobs, like a weekend digest email: fires at 10:00, and stays completely silent Monday through Friday.
Last updated
In plain English
- Fires at 10:00 on Saturday and Sunday
- Silent Monday through Friday
Why it’s written this way
The day-of-week field takes a comma list, 6,0 — Saturday and Sunday — while day-of-month stays *, so nothing else about the date matters. Minute 0, hour 10 pin the time itself to 10:00.
Cron accepts Sunday as both 0 and 7; this expression uses 0, but 6,7 would mean exactly the same two days. Either is correct — the point is to pick one convention and stay consistent across a codebase.
Edge cases to know
- →Because day-of-month is left as *, day-of-week alone decides the days. If day-of-month were ALSO restricted, cron would OR the two fields together instead of intersecting them, which is rarely the intent.
- →A weekend-only job is easy to forget about during on-call rotations that assume 'daily' cadence for everything — document the gap explicitly rather than relying on someone noticing the 6,0.
- →Public holidays that fall midweek aren't covered by this schedule and never will be — cron has no calendar awareness beyond weekday number and date.