AUTOMATION TOOL / 007
Cron expression builder.
Construct and verify a five-field cron schedule, understand what it means, and see exactly when it runs next.
BUILD THE SCHEDULE
This target supports CRON_TZ, so the expression stays in UTC and remains daylight-saving aware on the UTC server.
COMMON SCHEDULES
FIELD SYNTAX
* any value, list- range/ stepCOMMAND & OUTPUT
SCHEDULE ANALYSIS
● VALID
At 09:00 AM, Monday through Friday
Previewed in UTC. Daylight-saving changes are reflected by that timezone.
NEXT 10 RUNS
01Mon, Sep 21, 2026, 9:00:00 AM UTC2026-09-21T09:00:00.000Z
02Tue, Sep 22, 2026, 9:00:00 AM UTC2026-09-22T09:00:00.000Z
03Wed, Sep 23, 2026, 9:00:00 AM UTC2026-09-23T09:00:00.000Z
04Thu, Sep 24, 2026, 9:00:00 AM UTC2026-09-24T09:00:00.000Z
05Fri, Sep 25, 2026, 9:00:00 AM UTC2026-09-25T09:00:00.000Z
06Mon, Sep 28, 2026, 9:00:00 AM UTC2026-09-28T09:00:00.000Z
07Tue, Sep 29, 2026, 9:00:00 AM UTC2026-09-29T09:00:00.000Z
08Wed, Sep 30, 2026, 9:00:00 AM UTC2026-09-30T09:00:00.000Z
09Thu, Oct 1, 2026, 9:00:00 AM UTC2026-10-01T09:00:00.000Z
10Fri, Oct 2, 2026, 9:00:00 AM UTC2026-10-02T09:00:00.000Z
GENERATED BLOCK / CRONIE (LINUX)
# Target: Cronie (Linux) # Server timezone: UTC CRON_TZ=UTC SHELL=/bin/bash 0 9 * * 1-5 /path/to/command >> /var/log/job.log 2>&1
IMPLEMENTATION NOTE
Cron syntax and day-of-month/day-of-week behavior can vary between platforms. Confirm the expression against the scheduler that will actually run it. Traditional cron commonly evaluates day-of-month and day-of-week with OR behavior when both are restricted.