jellyseerr
jellyseerr copied to clipboard
Fallenbagel
Availability of media doesn't change after a full scan.
Description
After deleting media in Jellyfin, Jellyseerr still marks the media as Available. So you can't request it a 2nd time. Even when running a manual Full Library scan it still marks it as Available.
Version
1.1
Steps to Reproduce
- Request media in Jellyseerr.
- Delete it from Sonarr/Radarr/Jellyfin.
- Notice that Jellyfin doesn't show the movie anymore in the library.
- Do a Full Manual Library Scan in Jellyseerr.
Screenshots
All this media has been deleted from my server already, jellyseerr marks it as Available.
Logs
No response
Platform
desktop
Device
Windows
Operating System
Ubuntu
Browser
Edge
Additional Context
No response
Code of Conduct
- [X] I agree to follow Overseerr's Code of Conduct
Do you have available scan enabled on sonarr and radarr services? Because if so it will do that. Otherwise it shouldn't (I just tested)
Do you have available scan enabled on sonarr and radarr services? Because if so it will do that. Otherwise it shouldn't (I just tested)
Scan is enabled on both Sonarr and Radarr since the setup. I just double-checked and they are still enabled. I also tried disabling and re-enabling them but after a Radarr and Sonarr scan the media is still marked as available.
You could create a new instance, this time disable scan on sonarr and radarr and it won't mark anything as available. Or you can manually remove data for each one after the other (not ideal). The reason why they are marked as available is because you had scan from both services turned on when you set it up.
Steps:
- remove config folder
- remove container
- create new container
- set it up but this time have the services enable scan turned off.
That should solve it
I'm having the same problems, the above steps didn't solved them.
Could you come over to discord so its easier to troubleshoot?
Did this ever make it over to discord. Went and searched but could not find it. Having the same issue on unraid server build.
Did this ever make it over to discord. Went and searched but could not find it. Having the same issue on unraid server build.
It did. But I recommend to make a new support thread on discord and we can follow the troubleshooting steps. I think I already know your issue so
:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:
-
v1.8.0 - GitHub release
Your semantic-release bot :package::rocket: