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

Run Checks Modal

Review detailed backup job run information, examine objects and errors, and mark runs as reviewed.

Overview

The Run Checks page is the primary daily operational tool for reviewing backup job runs. This is where you spend most of your time during daily backup review.

💡 Your Daily Starting Point:
Start here every morning. The goal is to have this page completely empty - meaning all runs have been reviewed. Even successful backups must be marked as reviewed to clear the page.

The page provides:

Accessing Run Checks

To access the Run Checks page:

  1. Navigate to Run Checks in the main navigation menu
  2. Available to Admin and Operator roles only
  3. Viewers cannot access the Run Checks page
  4. The page shows all unreviewed runs by default
💡 Start Here Every Day:
This is your primary daily workflow page. Open it first thing in the morning and work through all runs until the page is empty.

Page Layout

The Run Checks page is organized by job, with each job showing its unreviewed runs:

1. Job List

The page displays jobs that have unreviewed runs:

2. Run Details per Job

When you click on a job, you see all its unreviewed runs:

💡 Review by Job:
Runs are grouped by job. When you mark a job as reviewed, all runs for that job are marked as reviewed simultaneously. The job then disappears from the Run Checks page. By default, only unreviewed jobs are shown. Admins can toggle "Include reviewed" to see all jobs including those already reviewed.

Run Details Sections

Status Information

At the top of the run details:

Backup Objects

A table showing individual backup items (VMs, servers, files, etc.):

Column Description
Name Object name (e.g., VM name, server name, file path)
Type Object type (e.g., VM, Server, Repository) - if available from parser
Status Object-level status (Success, Warning, Failed)
Message Error or warning message for this object (if any)
💡 Object Availability:
Backup objects are only shown if the parser extracted them from the email. Not all backup software emails include object-level details. If no objects are shown, the parser didn't detect individual items in the email.

Cove / Cloud Connect Summary Panels

For runs imported via the Cove API or Veeam Cloud Connect (no source email), the modal hides the email section and shows a structured summary panel instead:

See Cove Data Protection and Veeam Cloud Connect for the underlying data flow.

💡 Cove same-day suppression:
For Cove jobs, once the first complete success run on a given local day is recorded (status Success with all object statuses Success), all newer Cove runs on that same day are hidden from Run Checks — regardless of status. This prevents duplicate review of the same day's backup activity.

Email Content

For email-imported runs, the original email body from the backup software is displayed in an embedded iframe:

Email Metadata

Above the email body, metadata is shown:

Download .EML

If EML storage is enabled, a download button allows you to save the original email file for external analysis or support requests.

Autotask Ticket Information

If Autotask integration is enabled and a ticket was created for this run, the modal shows:

💡 Autotask Integration:
Autotask ticket information only appears if the Autotask integration is enabled in Settings and a ticket was created for this run. See Autotask Integration for details.

Review Actions

Mark as Reviewed (Single)

For any run (success, warning, or failure):

  1. Click on a run in the list to view details
  2. Review the run details, backup objects, and any error messages
  3. Take action if needed (create ticket, remark, or override)
  4. Click the Mark as reviewed button
  5. All runs for this job are immediately marked as reviewed and the job disappears from the Run Checks page

Mark as Success (with optional override)

For warning or failed runs that should be treated as successful, use Mark as Success:

  1. Open the run details and click Mark as Success.
  2. The run is recorded as success-by-override and removed from the unreviewed list.
  3. A follow-up dialog asks "Apply override for future runs?" with two choices that persist beyond this single run:
  4. Choose a duration: 1 week, 1 month, or permanent (until manually disabled).
  5. The error text is pre-filled from the run's problem objects so you can review and trim it before saving.
💡 When to use which scope:
Use "Only this run" for one-off events, "This job" for issues specific to a single environment (e.g. a particular VM that always warns), and "All jobs" for known cosmetic warnings from a backup product that recur across many customers. Broader overrides are audit-logged with scope, duration, and source run details.

Mark as Reviewed (Bulk)

For efficiency, especially with successful backups:

  1. Select multiple job checkboxes in the Run Checks list
  2. Click Mark selected as reviewed button
  3. All runs for all selected jobs are marked as reviewed and disappear from the Run Checks page

This is particularly useful for quickly clearing successful backups that don't require investigation.

⚠️ All Runs Must Be Reviewed:
Even successful backup runs must be marked as reviewed to clear the Run Checks page. They're not individually investigated, but they still need to be marked so the page becomes empty. Use bulk review to quickly clear multiple successful runs at once.

Unmark Reviewed (Admin Only)

Admins can unmark a reviewed job if it needs to be re-investigated:

  1. Enable the "Include reviewed" toggle to show reviewed jobs
  2. Select a reviewed job from the list
  3. Click the Unmark reviewed button
  4. All runs for this job return to the unreviewed list

This is useful if new information about an issue comes to light after the job was marked as reviewed.

⚠️ Admin-Only Feature:
Only Admins can unmark reviewed runs. Operators can only mark runs as reviewed, not unmark them.

Linking Tickets and Remarks

From the Run Checks modal, you can create and link tickets or remarks to document issues:

See Remarks & Tickets for detailed instructions.

Common Workflows

Investigating a Failed Backup

  1. Open the Run Checks modal from Daily Jobs (click on the failed job row)
  2. The most recent run is automatically selected (the failure)
  3. Review the Backup Objects table to see which items failed
  4. Check the Message column for error details
  5. Scroll down to view the full email body for additional context
  6. If the issue requires followup, create a ticket
  7. If it's a known issue or no action is needed, mark the run as reviewed

Comparing Multiple Runs

  1. Open the Run Checks modal for a job with warnings
  2. Enable "Include reviewed" (Admin only) to see historical runs
  3. Click through runs in the left-side list
  4. Compare which objects failed/succeeded across different runs
  5. Identify patterns (e.g., same VM fails every time vs. intermittent failures)

Reviewing Warnings with Overrides

  1. Open a job with a warning badge from Daily Jobs
  2. Notice the override indicator showing "Treated as success: [reason]"
  3. Review the backup objects to understand why the override was created
  4. If the override is still appropriate, mark the run as reviewed
  5. If the override is no longer appropriate, edit or remove it on the Overrides page

Troubleshooting Missed Jobs

  1. Open a job with "Missed" status from Daily Jobs
  2. The Run Checks modal shows recent runs
  3. Check the timestamps to confirm the job hasn't run today
  4. Look for patterns in historical runs (e.g., consistently misses Mondays)
  5. Create a ticket to investigate with the customer
  6. Mark the missed run as reviewed after creating the ticket

Best Practices

Troubleshooting

No Backup Objects Shown

If the Backup Objects section is empty:

Email Body Shows "No message content stored"

Can't Mark Run as Reviewed

Run List Is Empty

Next Steps

{% endblock %}