Cron expression tester › */10 * * * *
What does */10 * * * * mean?
Every 10 minutes. Runs at minute 0, 10, 20, 30, 40 and 50 of every hour — six times per hour.
A gentle polling cadence for feeds, webhooks retries, and status refreshes where a few minutes of lag is fine.
Next scheduled runs
Calculating…
Field-by-field breakdown
| Value | Field | Meaning |
|---|---|---|
*/10 | Minute (0–59) | every 10 step |
* | Hour (0–23) | every value |
* | Day of month (1–31) | every value |
* | Month (1–12) | every value |
* | Day of week (0–6, Sun=0) | every value |
Standard 5-field Vixie/POSIX cron: minute hour day-of-month month day-of-week. Cron uses the server's local timezone unless configured otherwise. Non-standard extensions (@daily, L, W, #, seconds) aren't evaluated here.
Open this schedule in the interactive tester →
Will you know if a every 10 minutes run is skipped?
Knowing when */10 * * * * should fire is only half of it. The failure that hurts is the silent one — the box was asleep, the trigger broke, the token expired, and nobody noticed. Cronpulse is a free dead-man's-switch: your job pings a URL each time it runs on this schedule, and if a ping goes missing, we alert you by email, Discord, Slack, or webhook.
Monitor a every 10 minutes job — free → No signup needed to start.
Related cron schedules
| Schedule | Meaning |
|---|---|
*/15 * * * * | Every 15 minutes |
*/30 * * * * | Every 30 minutes |
0 * * * * | Every hour (on the hour) |
0 */2 * * * | Every 2 hours |
0 */3 * * * | Every 3 hours |
All common cron expressions → · Monitor scheduled jobs → · Monitor an AI agent →