Skip to content
QuasarQuasar

Jobs and schedules

Admin ▸ Fleet ▸ Jobs lists background work: instance-wide jobs, per-host jobs, and older unmanaged jobs (visible, not controllable).

What the table shows

Section titled “What the table shows”

Each job’s scope, enabled state, schedule, last and next run, current state and latest result. Expand a per-host job to see each host.

Schedules can be periodic, limited to a time window and days, event-driven, or manual only.

Run now

Section titled “Run now”
  1. Open the job’s actions menu and select Run now.
  2. Select a host if prompted.
  3. Check the latest result in the job’s run history.

Disabled jobs cannot run, and an active job refuses a second run.

Edit a schedule

Section titled “Edit a schedule”

Managed schedules can be enabled, disabled, or given a new interval or window. A schedule locked by an environment variable names it; remove the variable and restart to edit it here.

The release detection job

Section titled “The release detection job”

platform.release_detect checks for new Quasar releases on the current channel. It installs nothing, unless Install updates automatically is on, in which case this schedule is the update window. It also sends the release notification, if set up.

  • Default: weekly, Monday, one-hour window from 02:00 UTC. Change it here like any managed schedule.
  • Check now on the Releases tab is the same as Run now. Both ignore the window.
  • The repository and token are environment settings (see Updates and releases). Setting the repository to off skips every run; empty means the default repository.

Results show on Updating Quasar.

Run history

Section titled “Run history”

Open a job for its recent runs, newest first, with result, message and timestamps. Check these before container logs.