Cron schedule reference

Cron every 10 seconds

Copy the expression, preview upcoming runs, or adjust the schedule below. Check compatibility before using it in your scheduler.

Cron expression

Every 10 seconds

Second: */10
Minute: *
Hour: *
Day: *
Month: *
Weekday: *

Common schedules

Scheduler syntax

Preview timezone

Next scheduled times

Previewed in UTC. This does not change your scheduler’s timezone.

Sun, 25 Oct 2026
12:39:40 UTC
Sun, 25 Oct 2026
12:39:50 UTC
Sun, 25 Oct 2026
12:40:00 UTC

Build a Unix schedule

Timing and scheduler compatibility

Standard Linux crontab has no seconds field. Use this expression only with a seconds-based scheduler that supports six fields.
Step values apply within their field and restart at its boundary; they are not elapsed-time timers.
Preview timezone does not configure your scheduler. Match its timezone; daylight saving changes can skip or repeat local times.

Use this schedule safely

Standard Linux crontab has no seconds field. Configure this six-field expression in a compatible seconds-based scheduler, such as node-cron. Do not paste it into crontab -e.

Cron starts commands but does not alert you when a job fails or never runs. Monitor this cron job to detect silent failures. Guarded entries intentionally skip nonmatching dates; configure monitoring for the intended schedule, not the guard’s daily or weekly checks.

Read the cron fields

Unix crontab has five fields: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–7, with 0 and 7 representing Sunday). Seconds-based syntax adds a seconds field (0–59) at the start.

* matches any value; , separates values; - defines an inclusive range.
/ steps through values within a field. */15 matches minutes 0, 15, 30 and 45.
When both day fields are restricted, Unix cron matches either day field, not both.

Read the crontab manual or the complete cron job guide for setup and troubleshooting.

Related cron schedules

Browse all cron expression examples