-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seasons that aren't available are marked as partially available when synced with Jellyfin #119
Comments
I just tried the other way too. Having season 3 without season 1-2 for example and i could not replicate the error. As you can see from my screenshot, I have season 3 downloaded and rhe previous seasons are still shown as unavailable and not requested. I have run the jellyfin recently added library scan as well as the full scan. Could you try recreating jellyseerr and checking if the same thing happens? Or try the |
I have the very same problem. Not all shows have such issues, mostly the new ones are without a problem. It seems like a regression problem. My feeling is that it is caused by jellyfin keeping some metadata about deleted seasons/episodes, however the jellyfin web ui can correctly determine so and wont show anything in the UI. On the other hand, jellyseerr does not handle this case and thus shows partially available / available status. Logging the queries and responses of jellyfin api would be helpful to see whats really happening. |
This what I have been thinking as well. There might be metadata leftover of some deleted seasons or episodes or like metadata there w no media. Jellyfin won't pick it up but jellyseerr would as it would look for the metadata instead of the video file |
Shouldn't be this marked as bug then? Jellyseer needs to do some validation or something else, because even 3rd party jellyfin clients don't display the series which jellyseerr sees as (partially) available - suggesting that this can be determined by the Jellyfin API. |
Yes I have the same issued and I was wondering what it is about. Is there any solution to this? |
For one thing though, we have to make sure if that is what is actually happening. I am entirely not sure myself either and I'll try and see if I can reproduce the same thing by generating some metadata for non-existent video files in jellyfin and see if jellyseerr picks it up. And also make sure that it can be validated through jellyfin api (I'm sure there must be a way, but I have yet to figure it out. Feel free to PR if you find a solution before me) |
One temporary solution I could think of is, deleting any leftover metadata from jellyfin and then removing the data of that show from jellyseerr and rescanning. That was jellyseerr will only see the season that is available and everything else will be seen as not requested |
Virtual seasons appeared as available / partially available, even though they were not even shown in the Jellyfin web UI. For more info see Fallenbagel#119
Virtual seasons appeared as available / partially available, even though they were not even shown in the Jellyfin web UI. For more info see Fallenbagel#119
Description
On every show I have with multiple seasons with only some downloaded, Jellyseerr incorrectly marks the missing seasons as "partially available" which prevents anyone from requesting them. I have noticed this happens only when doing a library scan with Jellyfin.
Without doing a library scan with Jellyfin and instead first setting up Sonarr with the "Enable scan" feature and running a Sonarr scan in Jobs & Cache, it correctly detects the undownloaded seasons as "Not requested". This can also be replicated by clearing data for the particular show and running a Sonarr scan - though it once again regresses to "partially available" once the Jellyfin library scan runs.
Version
1.10
Steps to Reproduce
Screenshots
How the show looks like in Sonarr (as you can see, only one season is downloaded):
And in Jellyfin, where you can see only the same one season is available:
Logs
No response
Platform
desktop
Device
PC
Operating System
Linux
Browser
Firefox
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: