1
Minute
0-59- Allowed
- 0-59
- Aliases
- —
*/15Design cron schedules, explain every field, simulate future runs, test reliability and export deployment-ready scheduler configuration.
422 IANA zones available. You can also type any IANA identifier supported by this runtime.
Describe the schedule as an operational intent, preview the exact five-field expression, then apply it to the engineering workspace.
Fixed cadence options divide 60 evenly, avoiding a shorter gap when cron resets the minute field at the next hour.
Expression preview
*/15 * * * *Edit individual fields without losing direct access to the cron expression.
Select a field to connect the expression with its scheduling meaning.
Read five-field cron precisely, then compare the parts that change across production schedulers instead of assuming every cron dialect behaves the same way.
Current target
Unix / crontab
1
0-59*/152
0-239-173
1-311,154
1-12JAN,MAR,SEP5
0-7MON-FRIUpcoming instants calculated using the selected time zone.
Reference: Oct 6, 2026, 1:43 AM
Simulation is Unix-based. Other targets are analyzed or exported without pretending to run their native engine.
Generate a starting configuration for the selected scheduler.
# crontab timezone is host/daemon configuration; ensure it evaluates in Europe/Madrid.
*/15 9-17 * * 1-5 ./job.sh
File: devkit-crontab.txt
Start from curated operational recipes and load their schedule context into the workspace.
Run a lightweight recurring task every five minutes.
*/5 * * * *Run once each weekday at the start of the working day.
0 9 * * 1-5Run every quarter hour from 09:00 through 17:59 on weekdays.
*/15 9-17 * * 1-5Run once per day at local midnight.
0 0 * * *Run a weekly backup every Sunday at 02:30.
30 2 * * 0Generate a report at 08:00 on the first day of each month.
0 8 1 * *Run a health check at the top of every hour.
0 * * * *Run maintenance at 03:15 every day.
15 3 * * *Assert whether a specific UTC instant should or should not trigger the current schedule.
Add assertions to protect a production schedule from regressions.
Preview upcoming runs in a selected time zone and inspect DST-sensitive behavior before deployment.
Check portability and generate configuration for Unix cron, GitHub Actions, Kubernetes, Dagu, Quartz and AWS EventBridge.
Parsing, tests and simulation run locally. Cron Studio designs schedules; it does not execute production jobs.