*/10 * * * *
Cron reads this as: every 10th minute.
Next 5 runs
Computed in your browser's local time zone. Cron itself evaluates against the server's zone, which on most cloud hosts is UTC — see time zones & DST if that distinction matters here.
- Calculating…
When to use this schedule
Six runs an hour, landing on :00, :10, :20, :30, :40 and :50. A good fit for syncs and imports where a ten-minute staleness window is fine and you would rather not pay the overhead of a tighter loop — feed ingestion, cache refresh, cleaning up expired sessions.
What to watch out for
Ten minutes is long enough that a failed run leaves a visible gap, so this is the interval at which it starts being worth logging each run's outcome rather than relying on mail you never read. Redirect output with >> /var/log/job.log 2>&1 and have the script exit non-zero on failure.
The crontab line
*/10 * * * * /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1Redirect the output somewhere you will actually read it — by default cron mails it, and on a host with no mail transport that means it is discarded. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
*/5 * * * * | Every 5 minutes |
*/15 * * * * | Every 15 minutes |
*/30 * * * * | Every 30 minutes |
Build your own
Need something this page does not cover? Compose it field by field in the visual builder, or paste an expression you already have into the explainer for a per-field breakdown. The examples library collects sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.