Every 10 Minutes
*/10 * * * * 0 */10 * * * ? */10 * * * * */10 * * * ? * 0 */10 * * * * */10 * * * * Runs every 10 minutes — at :00, :10, :20, :30, :40, :50 of every hour, every day.
Use in your stack
# Run every 10 minutes
*/10 * * * * /usr/local/bin/poll.sh
{ "cron": "0 */10 * * * ?", "timezone": "UTC" }
apiVersion: batch/v1
kind: CronJob
metadata:
name: poll
spec:
schedule: "*/10 * * * *"
jobTemplate:
spec:
template:
spec:
containers:
- name: poll
image: my-image:latest
restartPolicy: OnFailure
cron(*/10 * * * ? *)
@Scheduled(cron = "0 */10 * * * *")
public void every10Minutes() { /* ... */ }
on:
schedule:
- cron: '*/10 * * * *'
Next runs
Pick a timezone to see when this expression fires next.
Next 10 runs
- 012026-07-03T17:00:00.000Z
- 022026-07-03T17:10:00.000Z
- 032026-07-03T17:20:00.000Z
- 042026-07-03T17:30:00.000Z
- 052026-07-03T17:40:00.000Z
- 062026-07-03T17:50:00.000Z
- 072026-07-03T18:00:00.000Z
- 082026-07-03T18:10:00.000Z
- 092026-07-03T18:20:00.000Z
- 102026-07-03T18:30:00.000Z
Variations
Common use cases
- Polling external APIs where 10-minute freshness is enough.
- Refreshing cached dashboards or summary views.
- Re-checking certificate expiration or background sync status.
- Sending batched notifications without flooding users.
Gotchas
- AWS EventBridge needs the 6-field form: `*/10 * * * ? *`.
- Quartz needs seconds + ?: `0 */10 * * * ?`.
- If many jobs use `*/10 * * * *`, they fire on the same wall-clock instant — add per-job jitter to avoid load spikes.
Every 10 minutes — */10 * * * * — is one of the most common high-frequency schedules in production. Fast enough to feel near-real-time for most polling needs, slow enough to keep log volume and infrastructure cost manageable.
Frequently asked questions
What does `*/10 * * * *` mean?
The `*/10` in the minute field means "every 10th minute starting from 0." So the job fires at :00, :10, :20, :30, :40, and :50 of every hour. The remaining four asterisks mean any hour, any day of the month, any month, and any day of the week.
Does this run exactly 6 times per hour?
Yes — 6 invocations per hour, 144 per day. Note that `*/10` always starts from 0, not from "every 10 minutes from when I added the job." Cron has no concept of relative-to-start scheduling.
How do I express "every 10 minutes" in Quartz?
Use `0 */10 * * * ?` — the leading `0` is the seconds field (fire at the top of each minute), and `?` is the day-of-week placeholder since day-of-month is set. Quartz requires either day-of-month or day-of-week to be `?`.
Will jobs ever overlap with `*/10 * * * *`?
Only if your job takes longer than 10 minutes. If overlap matters, set `concurrencyPolicy: Forbid` on a Kubernetes CronJob, wrap with `flock` on Linux, or check for an existing run inside your script.
Browse all cron patterns
Every schedule Cronuru documents, with its expression and code snippets for six dialects.