Loading
Visitar URL original
Paste a crontab line from a CI schedule, a Kubernetes CronJob or a GitHub Actions workflow and see what it means, field by field, with the next times it runs. Everything stays in your browser.
minute hour day-of-month month day-of-week, or a macro such as @daily
At 09:00 on weekdays
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute 0 |
| Hour | 9 | hour 09:00 |
| Day of month | * | every day of the month |
| Month | * | every month |
| Day of week | 1-5 | Monday through Friday |
Working out the next runs...
Standard five-field cron: minute, hour, day of month, month and day of week. It reads lists, ranges, steps such as */15 and 1-10/2, month and weekday names such as JAN and MON, and the macros @hourly, @daily, @weekly, @monthly and @yearly. Seconds and year fields (Quartz style) and Jenkins H syntax are not supported.
Classic cron runs the job on days that match either one. So 0 0 1 * 1 runs at midnight on the first of every month and also every Monday. If either field starts with *, both have to match.
The tool steps through the calendar from the current time and lists the next five times the schedule fires, in UTC or in your local time. A schedule that can never run, such as 0 0 31 2 *, says so instead of searching forever.
No. Parsing, describing and working out the run times all happen in your browser. Nothing you type is uploaded.
CODERCOPS builds reliable backends, data pipelines, and full-stack applications for startups and enterprises.