[Bug]: Removed entries prevented from re-discovery in some cases
Author: mm12Created Dec 12, 2025Updated Sep 11, 2026
LabelsType: BugTagStudio: LibraryPriority: Medium
Checklist
- I am using an up-to-date version.
- I have read the documentation.
- I have searched existing issues.
TagStudio Version
Alpha 9.5.6
Operating System & Version
Win11
Description
If you 'remove unlinked entries' (which usually means the file at that path no longer exists), any future files at that same path cannot be discovered by TagStudio in some cases. Speculation: Perhaps the path remains cached as populated by SQLAlchemy.
Expected Behavior
Once a file is unlinked, TagStudio should behave as if the paths associated with those entries have never been populated.
Steps to Reproduce
- Add an entry in a library path such as
abc/1.png - refresh library
- Delete
abc/1.png- suppose you discover this is actually page 2, and are going to download all pages at once from one source. - Check for unlinked entries. remove any unlinked entries
- Replace
abc/1.pngwith new file (ie, all pages) abc/1.pngwill not populate, but other pages will - becauseabc/1.png
Logs
No response
Source: TagStudioDev/TagStudio