Find the 02:00 pile-up before it happens
Add the schedules that share a database, a queue or a host. Each can have its own dialect and time zone — a Kubernetes CronJob in UTC next to a Quartz trigger in Europe/Paris — and CronViewer converts everything to instants before comparing. Collisions are runs from different schedules within your tolerance (for example 60 seconds). With an expected duration per job, overlaps show executions that would run concurrently, including a job overlapping its own next run.
The timeline draws one lane per schedule for the next seven days, so clusters are visible at a glance. Results are a simulation of schedule times only: real execution delays, retries and queueing are not modelled.
Try these
Questions
Can I compare a schedule with its converted version?
Yes — the Convert tab already does this automatically and lists every run that differs. Use Compare for different jobs that must not clash.
How many schedules can I compare?
Up to six at once, over windows of 1 to 31 days.