Continue watching not working at all

[fromage9747]

got 10.9.6, seems to be working. now its just the slow search to wait for a fix for! Cheers!

[fromage9747]

I spoke too soon... Movie got removed from continue watching...

[fromage9747]

I guess I am the only one that has the continue watching issue still broken

[ThomasPGH]

I just tried this here and it works. Well, apart from that if a film has multiple versions all of them show up in Continue Watching.
https://github.com/jellyfin/jellyfin/issues/12049

[fromage9747]

@ThomasPGH What did you try? There isn't any resolution in that GitHub issue. With multiple versions that is normal and has always been there.

[Efficient_Good_5784]

You're using Docker. Did you try starting over and making a new Jellyfin server? You don't have to delete your old server and its metadata. Just make a new container with a brand new Jellyfin server, add your media, then test if the issue persists.

Obviously, make a backup of metadata stored alongside your media in case you need it back.

[ThomasPGH]

@ThomasPGH What did you try?  There isn't any resolution in that GitHub issue.

I played a film that has two versions and forwarded about 10 minutes in, then stopped. It does appear in Continue Watching, but twice. Precisely, it appears as many times as the film has versions. My Metropolis for instance got 5 versions, which makes it appear 5 times in Continue watching. There's no resolution in that Github issue because it hasn't been fixed yet. That's still how it is now.

With multiple versions that is normal and has always been there.

Certainly not. That's a bug in 10.9.6, probably other 10.9 versions too. Even if you follow the logic that if there's more than one version of a film, only the version played 10 minutes in should appear in Continue Watching, and not the whole parade of existing versions.

10.8.13 behaved correctly (apart from Android TV but that one had to be a bug in the client).

[ThomasPGH]

I guess I am the only one that has the continue watching issue still broken

Could it be that you got weird values in the admin panel -> Playback ->Resume?

[fromage9747]

@ThomasPGH

Thanks for that, didn't even know those settings existed. I have never changed them.

Included settings in the screenshot below:

https://imgur.com/LdXwR6c

I don't believe this is the issue as not only will it remove from my continue watching but since 10.9.7, I have the same issue prior to 10.9.6 where it loses the resume status completely and I have to seek through and locate where I was.

It's really getting on my nerves... But I have kinda gotten used to this issue and so have my kids... We all now say, "Blady Jelylfin" when it comes to movie time in the evening. Really sad though, such a small thing that causes a headache. This is the ONE time that I regret having it in Docker and having Watchtower handle my updates... I would've never upgraded! 10.8 was bliss. Fast search, continue watching worked... Ahhh the good ol days...

[fromage9747]

Made a discovery today. Yesterday, the search was horrendously slow that I gave up trying to watch a movie with my kids on their profile and watched using mine. This movie did not lose its resume from seek nor did it get removed from my continue watching. I went and had a look at the one movie that did get removed and compared them.

The one that gets removed has name_of_movie.nfo, movie.nfo and movie.xml. Movie.nfo stores the current seek and all that jazz whilst the other two do not. The movie that didn't get removed from continue watching does NOT have a movie.nfo.

Where is the seek status then being stored? How can I force ALL of my movies to no longer use movie.nfo? I have disabled radarr from my movies a few days ago as that does do a periodic update, but that hasn't been running, and the issue is still happening.

All of these issues started when Jellyfin got updated to 10.9.x. None of the issues existed in 10.8.x.

Hopefully someone can point me in the right direction.

All movies have been created under the same library of "Movies" so they all have the same configured library settings.