Skip to content

Runs and Monitoring

Run detail pages show what is happening now and what happened previously.

Run detail tabs

Run details are organized into tabs. The exact tabs depend on the run mode and job configuration.

  • Statistics: timing, counts, errors, deletes, and current run measurements.
  • Files: scanned or transferred objects. Use search and filters to find paths, hashes, object identifiers, file types, or rename candidates.
  • Logs: run messages with search, level filtering, object filtering, and pagination.
  • Files in Transit: currently active file activity while a live run is moving data.
  • Run Charts: speed, processor, and memory trends where measurements are available.
  • Integrity Evidence: verification rows when integrity evidence is enabled.
  • Delta planning tabs: action plans and fallback details when a delta strategy is enabled.

Tabs with large row sets use pagination so the browser only loads the requested page.

What you can monitor

  • current status
  • file and volume progress
  • current and average Estimated Time of Arrival (ETA)
  • logs
  • active files
  • speed and progress history
  • provider limit snapshots where supported
  • integrity evidence rows when the job uses an integrity evidence mode
  • delta planning details when the job uses audit-based or local change-feed delta
  • queued remediation actions related to the run

Reading progress

During a run, the most useful signals are usually:

  • files transferred versus total files
  • transferred volume versus total volume
  • current ETA
  • average ETA

Cancellation

Cancel from the run detail page or from the job page when a run is still queued or active.

Search and filtering

Use tab search when the row count is high. Files, logs, scan issue tabs, duplicate groups, and evidence-style tables are designed to be reviewed page by page. Prefer narrow searches such as a path fragment, object identifier, hash, status, file type, or relevant log phrase.

Changing a search term resets the visible page to the first page of matching rows.

Remediation queue bookmark

When renames, timestamp fixes, or deletions have been queued from the current run, the remediation bookmark appears at the right edge of the page. Expand it to see totals by status:

  • queued
  • running
  • runner lost contact
  • cancel requested
  • completed
  • failed
  • canceled

Use the entries in the bookmark to jump back to the related tab. Failed actions remain visible so they can be reviewed or retried.

Excel reports

Excel reports are generated in the background. Large reports can take time, so the run detail page shows a generation notice and starts the download automatically when the workbook is ready.

When a run has integrity evidence rows, the Excel report includes a dedicated Integrity Evidence worksheet. The run detail page also exposes a Comma-Separated Values (CSV) download for the same evidence rows.

For very large runs, report generation may take longer than page calculations. Download needed reports before old run history is removed by the retention policy.

Delta run monitoring

For delta strategies, review the planning section before judging a run by transfer counts alone. A healthy delta run may apply only a few targeted actions, while a conservative run may show scoped fallback syncs.

For audit-based delta, check the provider activity window, cursor or watermark context, planned actions, and runner execution feedback.

For local change-feed delta, check the job detail local change-feed panel for preflight status, smoke-test result, watcher state, cursor status, and latest local event.

See also