PREVIEW A RULE. DO NOT GUESS THE CLOCK.
The same rule.
A different hour.
Inspect local and UTC run times side by side. See offset changes and parser-adjusted wall clocks before copying a schedule into your own system.
1. Make the timing explicit
minute · hour · day-of-month · month · day-of-week. Digits, names (JAN–DEC, SUN–SAT), * , - / only. At least one day field must be exactly *. No commands, seconds, @nicknames, L, W, #, ?, H or year fields.
Include seconds and an explicit Z or numeric offset, for example 2026-03-28T00:00:00Z. It is an instant, not a floating local wall time. Start years 1970–2090; search stops eight years after it.
This is a cron-parser simulation. Different schedulers handle clocks differently. No job will be created or run.
2. Read both clocks
| # | Local time & offset | UTC | Elapsed minutes | Clock notes |
|---|
The first elapsed interval is from your start instant; later intervals are between listed runs. Offset-change notes compare those instants only, not all transitions in between. An hour/minute mismatch means this parser compensated a missing wall-clock time. It does not mean your daemon will do the same.
Report includes the rule, zone, start, search limit and exact run timestamps. No hidden command is added. Review your target scheduler's documentation before use.