Five fields, decoded: plain-English meaning plus the next run times in your timezone and UTC — computed locally in your browser.
—
—
Field order: minute hour day-of-month month day-of-week. Supports
* , - /, month/day names (JAN, MON…) and
the classic quirk: when both day fields are restricted, cron fires when either matches.
30 4 1,15 * 5 does not mean "the 1st and 15th if they are Fridays" — it runs on
the 1st, the 15th, and every Friday. Standard cron treats the two day fields as OR
when both are restricted. This single rule explains most "why did my job run today?" mysteries.
The other classics: */n steps start from the field minimum (not from when you
deployed), cron has no seconds field, and the schedule runs in the server's timezone —
which is why the table above shows both your local time and UTC.
Testing the endpoint your cron job calls? ReqPad sends the same request from your phone — handy for verifying a scheduled webhook fires correctly without waiting for the schedule. See also the cURL converter and status code reference.
Test the endpoint your cron hits — six protocols, real auth, request history. Free to start.