Every minute Cron Expression (* * * * *)

* * * * * Open in Cron Expression Parser

Field by field

Field	Value	Matches
Minute	*	Every value
Hour	*	Every value
Day of month	*	Every value
Month	*	Every value
Day of week	*	Every value

Next run times

Example: the first 6 runs after January 1, 2026 (UTC).

Thu, Jan 1, 2026, 00:01
Thu, Jan 1, 2026, 00:02
Thu, Jan 1, 2026, 00:03
Thu, Jan 1, 2026, 00:04
Thu, Jan 1, 2026, 00:05
Thu, Jan 1, 2026, 00:06

Ready-to-use versions

crontab

* * * * * /path/to/command

Add the line with crontab -e. It runs in the server's time zone unless CRON_TZ or TZ is set.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: every-minute
spec:
  schedule: "* * * * *"
  timeZone: "Etc/UTC"
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: job
              image: busybox:1.36
              command: ["/bin/sh", "-c", "date; echo run"]

Set spec.timeZone (Kubernetes 1.27+); without it the schedule follows the controller manager's time zone, usually UTC.

GitHub Actions: GitHub Actions cannot run this schedule: its shortest interval is 5 minutes.

GitHub Actions always uses UTC, accepts intervals of 5 minutes or more, and may start scheduled runs late under load.

Quartz

0 * * * * ?

Quartz puts seconds first and needs ? in either day-of-month or day-of-week. Days are 1–7 from Sunday, so names are safer.

Spring

@Scheduled(cron = "0 * * * * *")

Spring @Scheduled(cron = …) takes six fields: seconds, then the usual five.

FAQ

› Is every minute the shortest interval cron supports?

Yes. Standard cron has minute resolution. For sub-minute jobs use a loop with sleep, a systemd timer, or a scheduler with a seconds field such as Quartz.

› Which time zone does * * * * * run in?

Cron uses the time zone of the machine or service that runs it. On Linux that is the system time zone unless CRON_TZ or TZ is set; Kubernetes CronJobs accept spec.timeZone; GitHub Actions always uses UTC.

› How can I check this schedule before deploying it?

Open * * * * * in the Cron Expression Parser on this site. It explains each field and lists the upcoming runs in your local time or UTC, right in your browser.