Description
I was hoping there would be a way to have Seerr track the watchlist items to make sure that items are not re-added to Radarr/Sonarr when they are deleted from them. To be clear, here is the flow I'm thinking:
- Add item to watchlist
- Item gets added to sonarr/radarr
- Item is then deleted from the filesystem
- Item is now missing, and Seerr adds the movie to be downloaded again
- The cycle repeats
Desired Behavior
What I'm suggesting is to have Seerr generate a unique fingerprint, perhaps using the date the item was watchlisted and its GUID in a hash, and tie it to the request in question. This way, when Seerr polls the watchlist again, it recognizes it has already processed that item and skips it.
Additional Context
No response
Search Existing Issues
Code of Conduct
Description
I was hoping there would be a way to have Seerr track the watchlist items to make sure that items are not re-added to Radarr/Sonarr when they are deleted from them. To be clear, here is the flow I'm thinking:
Desired Behavior
What I'm suggesting is to have Seerr generate a unique fingerprint, perhaps using the date the item was watchlisted and its GUID in a hash, and tie it to the request in question. This way, when Seerr polls the watchlist again, it recognizes it has already processed that item and skips it.
Additional Context
No response
Search Existing Issues
Code of Conduct