Repository navigation
Feature Request: Dir Scan – per-item status overview and reset/reprocess action #2511
Replies: 2 comments
Agent BriefCategory: enhancement Current behavior: Recovery today is directory-wide only. Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call: whether Dir Scan gets a full tracked-item browser, and where it belongs in the Dir Scan tab. |
|
I dug into the root cause of this while working on #3803, so I'm adding it here since the triage above left revalidating A The docs disagree with each other here. If they should reopen, I'd check the stored hash with |
Uh oh!
There was an error while loading. Please reload this page.
Please bear with my if i am thinking wrong :)
Problem
Dir Scan persists the processing state of files in
dir_scan_files.Once an item reaches a final state such as:
matchedno_matchalready_seedingfuture scans can skip it with:
This is normally correct, but it becomes a problem when the underlying situation changes.
Example:
A previously matched torrent may have been removed from qBittorrent or its hardlink tree may no longer exist. The media file itself is still present, but Dir Scan will not search for it again because the persisted state remains
matched.Currently, recovering a single item requires either:
dir_scan_files.A full directory reset is unnecessarily broad, especially for large media libraries.
Proposed UI
Add a Dir Scan tracked items/status view for each configured directory.
The page could show a searchable/filterable list containing fields such as:
Example.Movie.mkv<file path>matchedReset / ReprocessThe important part would be a per-item action:
Reset scan state
After confirmation, qui should remove/reset only the selected tracked item so that the next Dir Scan can discover and process it again.
For example, internally this could behave similarly to deleting the relevant
dir_scan_filesrow:The next manual, scheduled, or webhook scan would then treat that file as unseen and perform the normal matching/search/injection workflow again.
Search
The status view should include a search field that searches persisted Dir Scan items by:
Example:
Result:
Reset confirmation
Clicking Reset scan state should show a confirmation dialog:
Buttons:
Expected behavior
The action should:
Conceptually:
Optional enhancement: Reset & Scan
In addition to:
Reset scan state
it would be useful to offer:
Reset & Scan
This would reset the selected state and immediately trigger a targeted Dir Scan for that item's path.
That would make recovery a single UI operation instead of requiring a reset followed by a separate webhook/manual scan.
Why this would be useful
This provides a clean recovery mechanism for cases where:
matchedstate is no longer validMost importantly, it avoids requiring users to manipulate the database manually or reset thousands of unrelated Dir Scan entries.
All reactions