Cron expression
Every 10 minutes
*/10 * * * *
Runs at 00, 10, 20, 30, 40 and 50 minutes past every hour, 144 times a day.
Runs per month
≈ 4,320
Next run (UTC)
Thu 14:20
On CronEngine
From the Starter plan
What each part means
| Minute | */10 | every 10 minutes |
| Hour | * | every hour |
| Day of month | * | every day of the month |
| Month | * | every month |
| Day of week | * | every day of the week |
Next runs
- 1 Thursday 22 October 2026 14:20 UTC
- 2 Thursday 22 October 2026 14:30 UTC
- 3 Thursday 22 October 2026 14:40 UTC
- 4 Thursday 22 October 2026 14:50 UTC
- 5 Thursday 22 October 2026 15:00 UTC
See these in your own timezone, or change the schedule →
Good to know
- A good default when every 5 minutes feels like too much and every 15 too little. 10 divides 60, so the runs are always ten minutes apart.
- The same schedule can be written as 0,10,20,30,40,50 * * * *. Both mean exactly the same.
Typical uses: Sending queued emails in batches, updating search indexes, clearing temporary files.
Copy and paste
*/10 * * * * /path/to/script.sh
on:
schedule:
- cron: '*/10 * * * *'
GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy. How to start it on time.
Schedule::command('your:command')->everyTenMinutes();
Variations
| 5-59/10 * * * * | Every 10 minutes, at 05, 15, 25 and so on |
| */15 * * * * | Every 15 minutes → |
Questions
What is the cron expression for every 10 minutes?
*/10 * * * *. Runs at 00, 10, 20, 30, 40 and 50 minutes past every hour, 144 times a day.
Can GitHub Actions run every 10 minutes?
Yes, with cron: '*/10 * * * *'. GitHub Actions reads this in UTC, and scheduled runs can start late when GitHub is busy.
More schedules: minutes
← All cron schedules · Cron cheat sheet · Cron expression generator