Skip to main content
Version: v3

Cron spec

CRON Expression Format

A cron expression represents a set of times, using 6 space-separated fields.

Field nameMandatory?Allowed valuesAllowed special characters
SecondsYes0-59* / , -
MinutesYes0-59* / , -
HoursYes0-23* / , -
Day of monthYes1-31* / , - ?
MonthYes1-12 or JAN-DEC* / , -
Day of weekYes0-6 or SUN-SAT* / , - ?

Note: Month and Day-of-week field values are case insensitive. "SUN", "Sun", and "sun" are equally accepted.

Special Characters

Asterisk ( * )

The asterisk indicates that the cron expression will match for all values of the field; e.g., using an asterisk in the 5th field (month) would indicate every month.

Slash ( / )

Slashes are used to describe increments of ranges. For example 3-59/15 in the 1st field (seconds) would indicate the 3rd second of the minute and every 15 seconds thereafter. The form "*/..." is equivalent to the form "first-last/...", that is, an increment over the largest possible range of the field. The form "N/..." is accepted as meaning "N-MAX/...", that is, starting at N, use the increment until the end of that specific range. It does not wrap around.

Comma ( , )

Commas are used to separate items of a list. For example, using "MON,WED,FRI" in the 6th field (day of week) would mean Mondays, Wednesdays and Fridays.

Hyphen ( - )

Hyphens are used to define ranges. For example, 9-17 would indicate every hour between 9am and 5pm inclusive.

Question mark ( ? )

Question mark may be used instead of '*' for leaving either day-of-month or day-of-week blank.

Predefined schedules

You may use one of several pre-defined schedules in place of a cron expression.

EntryDescriptionEquivalent To
@yearly (or @annually)Run once a year, midnight, Jan. 1st0 0 0 1 1 *
@monthlyRun once a month, midnight, first of month0 0 0 1 * *
@weeklyRun once a week, midnight on Sunday0 0 0 * * 0
@daily (or @midnight)Run once a day, midnight0 0 0 * * *
@hourlyRun once an hour, beginning of hour0 0 * * * *
@minutelyRun once a minute, beginning of minute0 * * * * *
@manuallyNever runsN/A


You may also schedule a job to execute at fixed intervals. This is supported by formatting the cron spec like this:

	@every <duration>

where "duration" is a string accepted by time.ParseDuration

For example, "@every 1h30m10s" would indicate a schedule that activates every 1 hour, 30 minutes, 10 seconds.

Note: The interval does not take the job runtime into account. For example, if a job takes 3 minutes to run, and it is scheduled to run every 5 minutes, it will have only 2 minutes of idle time between each run.

Fixed times

You may also want to schedule a job to be executed once. This is supported by formatting the cron spec like this:

    @at <datetime>

Where "datetime" is a string accepted by time.Parse in RFC3339 format

For example, "@at 2018-01-02T15:04:00Z" would run the job on the specified date and time assuming UTC timezone.

Time zones

Dkron is able to schedule jobs in time zones, if you specify the timezone parameter in a job definition.

If the time zone is not specified, the following rules apply:

All interpretation and scheduling is done in the machine's local time zone (as provided by the Go time package

Be aware that jobs scheduled during daylight-savings leap-ahead transitions will not be run!

If you specify timezone the job will be scheduled taking into account daylight-savings and leap-ahead transitions, running the job in the actual time in the specified time zone.