Daily
0 22 * * *
Run once a day at 22:00.
This preview is live: the table below shows the actual next run times for 0 22 * * * in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.
What 0 22 * * * means
0 22 * * * fires at 10pm. It is an evening slot that catches the full day's data while still leaving the small hours free for heavier overnight maintenance, a good place for an end-of-day export or the first stage of a multi-step nightly pipeline.
Ten at night is late enough that almost all of the day's activity is in, but early enough that a job which runs long will not collide with the 2-3am maintenance window.
Field-by-field breakdown
Unix cron has five fields. Here is what each one is doing in this expression:
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute = 0 |
| Hour | 22 | hour = 22 |
| Day of month | * | every day-of-month |
| Month | * | every month |
| Day of week | * | every day-of-week |
Every day at 10pm in every scheduler
The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target, the field count and day-of-week numbering differ between them.
| Scheduler | Expression | Copy |
|---|---|---|
| Unix / crontab | 0 22 * * * | |
| GitHub Actions | 0 22 * * * | |
| Kubernetes CronJob | 0 22 * * * | |
| Vercel Cron | 0 22 * * * | |
| Quartz | 0 0 22 * * * * | |
| Spring | 0 0 22 * * * | |
| AWS EventBridge | 0 22 * * * * |
When you would use 0 22 * * *
- End-of-day exports that feed overnight processing.
- First stage of a chained nightly pipeline.
- Snapshotting the day's final state before maintenance.
The gotcha worth knowing
If this is the first link in an overnight chain, do not hard-code the next stage to assume it finished. Use a completion marker so a slow 10pm run doesn't desync the 2am job.
People also search for
0 22 * * * FAQ
What does the cron expression 0 22 * * * mean?
0 22 * * * means: Run once a day at 22:00. 0 22 * * * fires at 10pm. It is an evening slot that catches the full day's data while still leaving the small hours free for heavier overnight maintenance, a good place for an end-of-day export or the first stage of a multi-step nightly pipeline.
How do I write "every day at 10pm" in GitHub Actions?
Use 0 22 * * * in the schedule's cron field. If this is the first link in an overnight chain, do not hard-code the next stage to assume it finished. Use a completion marker so a slow 10pm run doesn't desync the 2am job.
How do I write "every day at 10pm" for AWS EventBridge?
EventBridge uses six fields with a required year and a ? placeholder in one day field: 0 22 * * * *. Wrap it as cron(0 22 * * * *) in the console or CloudFormation.
What is the Quartz equivalent of 0 22 * * *?
Quartz is seconds-first with a trailing year, so the equivalent is 0 0 22 * * * *. Remember Quartz numbers Sunday as 1, the opposite of Unix.
Related cron patterns
More cron tools
Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.