Curated cron expression
Every 45 Minutes (approximation): 0,45 * * * *
True every-45-minutes needs multiple expressions or Quartz — 0,45 * * * * is a common hourly approximation.
Meaning at a glance
0,45 * * * *
Run at :00 and :45 each hour (not true 45-minute interval)
Twice per hour at :00 and :45 only.
Next-run example: At 10:07, next runs are 10:45, 11:00, 11:45.
How 0,45 * * * * works
Standard cron cannot express 'every 45 minutes' as a single simple step across hour boundaries.
0,45 * * * * runs twice hourly — not the same as a continuous 45-minute phase.
Use Quartz or multiple entries for exact 45-minute sliding intervals.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0,45 | Configured as 0,45 |
| Hour | * | Every value |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | * | Every value |
Good use cases
- Approximate polling
- Legacy crontab workarounds
Timezone and daylight-saving behavior
Neutral.
Not a sliding 45-minute window.
The expression does not contain a timezone. The scheduler supplies that context. Use the next-run preview above in the same IANA timezone as production, then confirm the target platform's own timezone rules.
Platform compatibility and converted expressions
The source expression is five-field Unix cron. Use the exact equivalent below rather than adding or removing fields by sight.
| Platform | Status | Expression | What to know |
|---|---|---|---|
| Unix crontab | Ready | 0,45 * * * * | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0,45 * * * * | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0,45 * * * * | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0,45 * * * * | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0,45 * ? * ? *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0,45 * * * * | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0,45 * * * * | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- Misunderstanding this pattern is a common production bug.
- Document actual fire times.
Frequently asked questions
What does the cron expression 0,45 * * * * mean?
0,45 * * * * means “run at :00 and :45 each hour (not true 45-minute interval).” Twice per hour at :00 and :45 only.
What are the next run times for 0,45 * * * *?
At 10:07, next runs are 10:45, 11:00, 11:45. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0,45 * * * * use?
Neutral.
Can I use 0,45 * * * * on every scheduling platform?
No. It is a five-field Unix expression. Some platforms accept it directly, while AWS EventBridge Scheduler, Spring, and systemd require the converted form shown in the compatibility table.