From 6106ae745867c7873768578208bce01a8c8d78d0 Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Mon, 23 Mar 2026 10:51:47 -0500 Subject: [PATCH] docs --- docs/docs/configuration/record.md | 2 ++ docs/static/frigate-api.yaml | 5 +++++ 2 files changed, 7 insertions(+) diff --git a/docs/docs/configuration/record.md b/docs/docs/configuration/record.md index 881c4de91..afd26c641 100644 --- a/docs/docs/configuration/record.md +++ b/docs/docs/configuration/record.md @@ -162,6 +162,8 @@ Normal operation may leave small numbers of orphaned files until Frigate's sched The Maintenance pane in the Frigate UI or an API endpoint `POST /api/media/sync` can be used to trigger a media sync. When using the API, a job ID is returned and the operation continues on the server. Status can be checked with the `/api/media/sync/status/{job_id}` endpoint. +Setting `verbose: true` writes a detailed report of every orphaned file and database entry to `/config/media_sync/.txt`. For recordings, the report separates orphaned database entries (DB records whose files are missing from disk) from orphaned files (files on disk with no corresponding database record). + :::warning This operation uses considerable CPU resources and includes a safety threshold that aborts if more than 50% of files would be deleted. Only run when necessary. If you set `force: true` the safety threshold will be bypassed; do not use `force` unless you are certain the deletions are intended. diff --git a/docs/static/frigate-api.yaml b/docs/static/frigate-api.yaml index 232e2e080..90fa505ec 100644 --- a/docs/static/frigate-api.yaml +++ b/docs/static/frigate-api.yaml @@ -6891,6 +6891,11 @@ components: title: Force description: "If True, bypass safety threshold checks" default: false + verbose: + type: boolean + title: Verbose + description: "If True, write full orphan file list to /config/media_sync/.txt" + default: false type: object title: MediaSyncBody MotionSearchMetricsResponse: