*/10 * * * *
Cron reads this as: every 10th minute.
Next 5 runs
These times are in your browser's local time zone. Cron itself uses the server's zone, which on most cloud hosts is UTC. If the difference matters here, see time zones & DST.
- Calculating…
When to use this schedule
It runs six times an hour, at :00, :10, :20, :30, :40 and :50. It suits syncs and imports where data up to ten minutes old is acceptable and a tighter loop would add overhead for no benefit. Typical jobs are feed ingestion, cache refreshes and cleanup of expired sessions.
What to watch out for
At ten minutes, a failed run leaves a visible gap in the data. From this interval up, log the outcome of each run instead of relying on cron mail that nobody reads. 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>&1Send the output to a log you will read. By default cron mails it, and on a host with no mail transport that mail is silently dropped. 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
If this page doesn't cover the schedule you need, 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 has sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.