關於 Cron 解析器
探測語法並預測執行時間
Cron dialects differ: Unix-style schedules, six-field formats, Quartz, and scheduler-specific extensions do not always interpret the same symbols identically. Always test the exact dialect and timezone used by the job runner.
點樣用呢個開發者工具
- Enter the expression and let the tool identify the likely dialect, or choose the format used by your scheduler.
- Read the field explanation and check the next several execution times.
- Compare the result with the production timezone, daylight-saving behavior, and the scheduler's own documentation.
私隱同資料處理
Cron parsing is local and does not require a network request. Do not paste operational schedules that expose private hostnames, customer information, or internal incident details unless they are safe to share.
相關開發者工具
常見問題
Why does the same expression mean different things elsewhere?
Field counts, day-of-month rules, question marks, seconds, and timezone handling vary between cron implementations. Use the runtime's dialect, not a generic example.
Why should I preview more than one run?
A schedule can look correct for the first occurrence but behave unexpectedly across month boundaries, weekdays, or daylight-saving transitions.
Does this tool run my scheduled job?
No. It parses the expression and calculates preview times. The scheduler remains responsible for execution, permissions, retries, and monitoring.