Scheduled Jobs and Calendar

Scheduled jobs are the concept for the recurring work a fleet has to do without anyone watching: database backups, log rotation, vacuuming, certificate renewals and similar maintenance. In VibeControls, each job ties an action to a schedule and a target machine, and the calendar is designed to show all of them together so a team can see what runs where, and when.

Cron entries scattered across servers are easy to forget and hard to audit. Nobody sees the whole timetable, overlapping jobs collide, and a failed backup can go unnoticed for days. The design brings every schedule into one workspace view with status colors, so a failure shows up as a red entry on the calendar instead of as silence.

The first illustration is a month calendar with a Today button, previous and next controls, a switch between month, week, day and agenda views, and a Schedule Task button. Each day lists job chips named by job and target, marked green, amber or red, with a count of further jobs when a day is busy, and weekends are shaded. The second illustration opens one job, a nightly database backup on a production web server. Summary cards show the cron schedule, timezone, next and last execution, the executor with the action it runs, and a priority. An executions list records each run with its status, start and completion times and exit code, and a logs panel shows the captured output and run duration. An Execute Now button runs the job outside its schedule.

The calendar sits in the Automation section alongside actions, decks and the scheduler, so a job is designed to reuse the same actions that power one-click decks. Run results are meant to feed the fleet's health and audit views, giving on-call engineers and platform teams one place to confirm that routine maintenance actually happened.