{% extends "documentation/base.html" %} {% block doc_content %}

Daily Jobs View

Monitor backup jobs expected to run on a specific date, with smart schedule inference and status tracking.

Overview

The Daily Jobs view displays all backup jobs expected to run on a selected date, based on intelligent schedule inference from historical run patterns. It provides an overview of which jobs exist and their schedules.

💡 Daily Jobs vs Run Checks:
Daily Jobs is primarily for viewing which jobs exist and their schedules. For daily operational review work, use the Run Checks page instead - that's where you review and mark runs as complete. Daily Jobs may be deprecated in a future version.

Key features:

Accessing Daily Jobs

To access the Daily Jobs view:

  1. Navigate to Daily Jobs in the main navigation menu
  2. Available to Admin, Operator, and Viewer roles
  3. The view defaults to today's date in your configured timezone

Date Selection

At the top of the page, you can select which date to view:

💡 Timezone:
Dates are displayed in your configured timezone (set in Settings). Job schedules are inferred based on when jobs historically ran in that timezone.

Job Table Columns

The Daily Jobs table displays the following columns:

Column Description
Customer Customer name the job belongs to
Backup software Backup product (e.g., Veeam, Synology, NAKIVO)
Backup type Job type (e.g., Backup Job, Replication Job)
Job name Name of the backup job
Schedule Inferred schedule pattern (e.g., "Daily", "Weekly: Mon Wed Fri", "Monthly: 1st, 15th")
Last run Timestamp of the most recent job run
Status Current status indicator (Success, Warning, Failed, Missed, Expected)
Reviewed Checkmark if the job has been reviewed (only for non-success statuses)
💡 Admin-Only Column:
The Reviewed column is only visible to users with the Admin role. Operators and Viewers cannot see review status in the Daily Jobs table.

Status Indicators

Each job displays a status badge indicating its current state:

Status Badge Color Meaning
Success Green Job completed successfully with no warnings or errors
Success (Override) Blue Job had warning/failure but is treated as success due to an active override rule
Warning Yellow Job completed but with warnings (e.g., retry succeeded, partial backup)
Failed Red Job failed and did not complete successfully
Missed Gray Job was expected to run on this date but no run was detected
Expected White Job is expected to run later today (for future dates or today before the job runs)

Schedule Inference

BackupChecks automatically infers backup job schedules by analyzing historical run patterns. This eliminates the need to manually configure schedules for each job.

How Schedule Inference Works

The system examines the past 60 days of job runs to detect patterns:

Schedule Display

In the Schedule column, you'll see:

💡 Learning Period:
Schedule inference requires at least 10-14 days of historical runs to detect patterns accurately. Newly approved jobs may show "-" or "Irregular" until enough data is collected.

Override Badges

Jobs with active overrides display a small badge next to the job name. Overrides are used to handle known issues or exceptions (e.g., "treated as success due to known warning").

To view override details:

  1. Look for jobs with override badges in the Daily Jobs table
  2. Click on the job row to open the Run Checks modal (see next section)
  3. The modal will show which overrides are applied to the job run

Ticket and Remark Indicators

Jobs linked to active tickets or remarks display indicator icons:

These indicators help you quickly identify jobs with known issues or ongoing investigations.

Viewing Job Details

To view detailed information about a job run:

  1. Click on any job row in the Daily Jobs table
  2. The Run Checks modal opens, showing:

See Run Checks Modal for detailed information about reviewing job runs.

Reviewing Jobs

For jobs with warnings or failures, you can mark them as reviewed after investigating:

  1. Click on the job row to open the Run Checks modal
  2. Review the job details, objects, and any error messages
  3. Click Mark as reviewed to acknowledge you've investigated the issue
  4. The job is marked as reviewed and removed from the unreviewed list
💡 Review Workflow:
Jobs with warnings or failures typically need investigation first. Successful runs can also appear in Run Checks until they are explicitly marked as reviewed (often via bulk review). The Run Checks workflow helps you triage and clear the unreviewed queue.

Common Workflows

Morning Backup Review

  1. Open Daily Jobs (defaults to today's date)
  2. Review the status column for any red (Failed) or yellow (Warning) badges
  3. Click on jobs with issues to open the Run Checks modal
  4. Investigate the failure/warning details and backup objects
  5. Create a ticket or remark if followup is needed, or mark as reviewed if it's a known issue
  6. Repeat for all jobs with issues

Checking Previous Day's Jobs

  1. Open Daily Jobs
  2. Click the Previous button to go back one day
  3. Review jobs that ran yesterday
  4. Look for "Missed" status - jobs that were expected but didn't run

Identifying Schedule Changes

  1. Notice a job appearing on an unexpected day
  2. Check the Schedule column to see the inferred pattern
  3. If the schedule changed recently, it may take 10-14 days for the system to detect the new pattern
  4. Contact the customer if a job unexpectedly stops appearing on expected days

Best Practices

Troubleshooting

Job Not Appearing in Daily Jobs

If a job doesn't appear on a date when you expected it:

Schedule Shows "Irregular" or "-"

Cove Workstations Don't Show "Missed"

Job Shows "Missed" but Actually Ran

Next Steps

{% endblock %}