Cron Expression for Every 10 Minutes
*/10 * * * **/10 * * * * runs at :00, :10, :20, :30, :40 and :50 every hour — six fixed minutes, the same ones everywhere the expression is used.
Next runs, in your timezone
Reading the step
The step divides the 0–59 minute range, so */10 is shorthand for the list 0,10,20,30,40,50. Runs are pinned to those minutes; installing the job at :07 does not make it run at :17.
*/10 * * * * /path/to/job.sh >> /var/log/myjob.log 2>&1When ten minutes is a polling loop
A lot of every-10-minutes jobs are really "check if there is new data". If the check is cheap, fine. If it hammers a database, consider event-driven triggers or at least an offset phase (3-53/10) so a fleet of pollers does not synchronize.
Equivalent expressions
0,10,20,30,40,50 * * * *— explicit list — identical schedule3-53/10 * * * *— same cadence offset to :03, :13, …
Run a SQL query on this schedule
If the job behind this schedule is a database query, you can skip the server and the crontab: SaturnSQL runs saved SQL queries on a cron expression — this exact syntax, with a real timezone field — and delivers the results to Google Sheets or Slack. Minimum interval 5 minutes.