Qaynaq LABS · TOOLS

CRON · DECODE

* * * * 4

This cron expression runs every minute on Thursdays (day-of-week 4, where 0 or 7 is Sunday).

Field-by-field

PositionValueMeaning
minute * Every minute
hour * Every hour
day-of-month * Every day of the month
month * Every month
day-of-week 4 Thursday (where 0 or 7 is Sunday)

Next fires (UTC)

  • 2023-11-02 00:00:00 UTC
  • 2023-11-02 00:01:00 UTC
  • 2023-11-02 00:02:00 UTC
  • 2023-11-02 23:59:00 UTC

Watch out for

  • The day-of-week field (4) conflicts with the day-of-month field (*) in some cron implementations. Most modern systems (e.g., Linux cron) prioritize day-of-week over day-of-month when both are specified, but this is implementation-dependent.

Equivalent forms

  • 0 * * * 4 (runs at the top of every hour on Thursdays)
  • */1 * * * 4 (equivalent to *, runs every minute on Thursdays)
  • * * * * THU (using day name instead of number)

About cron expressions

Cron is the standard format Unix-like systems use to schedule recurring jobs: five space-separated fields representing minute, hour, day of month, month, and day of week. The syntax is dense but unambiguous — once you can read it, you can express almost any schedule.

Qaynaq Labs' cron decoder works in both directions: paste an existing expression to read it out in English, or describe a schedule and get a valid cron string back. Each result includes the next few fire times, any caveats (like end-of-month edge cases), and equivalent alternative forms.

Frequently asked

Does this run every minute on all Thursdays or only at specific times?

It runs every minute (00, 01, 02, ..., 59) on every Thursday.

What happens if I set both day-of-week and day-of-month to specific values?

Most cron implementations prioritize day-of-week over day-of-month. For example, '* * 15 * 4' would run on the 15th of the month only if it's a Thursday, otherwise it would run on the nearest Thursday.