shadcn.io is not affiliated with official shadcn/ui
Scheduled Jobs Timeline Monitoring Block for Ark UI
A day of six scheduled jobs as a Gantt: finished, failed, missed and still-to-come runs on a 24-hour axis, overlaps stacked, and a read-out of any run with its exit code, delay and the job's next run.
Installation
Overview
Find the runs a scheduler skipped, not just the ones that failed, with this one-day timeline for React with Ark UI. It is Cronloft, a scheduled-jobs monitor, and it draws six job lanes across 24 hours. Each run is a bar from its start to its end, never narrower than 18 minutes; overlapping runs of one job stack in a second row. A finished run is solid, a failed run is outlined with a cross, a missed run is a hatched empty box at its scheduled time, and a run still to come is dashed. A line marks the fixed time "now". The chart is a named scroll region that keeps the job names in view as it scrolls, and every run is a button named with its job, time, length and result. Choosing one reads it below: start, duration, exit code, the delay between scheduled and started, and the job's next run ("16:00, in 1 h 50 min"). The header counts the missed runs and overlaps. Guides draw the frame and its bands. For cron dashboards, batch windows and post-incident reviews.
FAQ
How do I load my own runs?
Edit RUNS: each has its job, the scheduled minute of the day, the start minute (or -1 if it never started), the length, the state (done, failed, missed, next), the exit code and the row to draw it in. NOW is the time of the marker; the header counts and the overlaps are derived.
Is anything measured?
No. The runs are typed, the time is fixed, and nothing calls a network or a scheduler. Choosing a run only reads it.
How are the states told apart?
By shape and fill, not colour: solid, outlined with a cross, hatched, dashed. The key above the chart names them and each button's name ends with the result.