Skip to main content

Create and manage jobs

A job saves drive selection, methods, schedule, and run options. Use jobs for predictable maintenance windows or for different policies on different volumes.

Create a job​

  1. Open Schedules and choose the create/new-job control.
  2. On General, enter a descriptive name.
  3. Choose Once, Recurring, or Screensaver and complete the applicable fields.
  4. Open Drives → Drives and method….
  5. Assign a method to at least one drive and, if needed, a minimum fragmentation percentage.
  6. Review Schedule, Options, Activity Monitor, and Files.
  7. Leave Batch disabled unless you need reviewed pre- or post-job commands.
  8. Choose Save.

New jobs start from the current global optimization options. Existing jobs retain their saved options, so review them after changing global defaults.

Example: weekly data-drive maintenance​

Give the task a name such as Weekly data-drive optimization. Select Recurring, choose a maintenance day and an appropriate start time, and assign a suitable method to the data drive. Enable reporting, set a maximum runtime if needed, and exclude processes that must not overlap.

Choose the method based on the media and results. Do not apply a traditional HDD sorting policy to an SSD simply because the job runs weekly.

Inspect or modify​

Open a job to view its saved settings. View mode is read-only. To make changes, select the modify/edit action, update the relevant tabs, and choose Save. Cancel discards unsaved edits.

If a configured drive is offline, the drive editor can show it as not currently present. Its saved configuration remains part of the job; saving other changes does not make the missing drive available.

Delete​

Select the intended job and use Delete. Review the confirmation. Deleting a job removes its scheduled configuration; use the drive's Stop control if an action is already running and you also want to end it.

Confirm that it ran​

Inspect the job's last-run information and Reports. The Next run field does not calculate the next execution time; use the saved schedule and run history to verify the task. See Scheduling.