SOLVED: Continue Watching not working for one user after update

[Confused-o-Screaming]

Ran updates for Jellyfin for the newest version and I saw that Continue Watching for my user is not being displayed on the home screen (works fine with other users). Items that I started, but don't finish disappear from the Next Up section like normal, but have to be manually located in my library to continue watching.

 Attempted to perform the migration again by deleting jellyfin.db and renaming library.db.old back to library.db. When I start the server, this error appears in the log and will repeat itself until I stop the service. Not using docker or anything, just straight apt. Any suggestions? I have this user account integrated with Symfonium so I'd like to resolve it without creating a new user profile for myself. I tried moving UserDatas from library.db to jellyfin.db, but that object doesn't exist in jellyfin.db.


Edit: this is then proper work around. I can't figure out how to change the solution post so I'm quoting it here. I also removed my error log: 

TL;DR: Run a full metadata replacement scan on libraries (leave trickplay and image replacement unchecked)

Nevermind, it is not working as expected. During the full scan, it imported a new movie. That was what I tested with. Played the movie, backed out around half-way through, and it showed up in 'Continue Watching'. Other movies that were in my library before, if I do the same thing, they do not show up. TV shows seem to work fine though.

So I picked a movie that was in my library that exhibits this "doesn't show up in Continue Watching" behavior, did a 'Refresh metadata' (Replace all metadata, leaving both replacing existing images and trickplay images unchecked), and then tried again.
And it showed up in 'Continue Watching'.
I'll keep poking. I kinda would like to avoid doing a 'Refresh metadata' on my entire library, but maybe that's the answer.

Edit: I think the refresh has finished and it is indeed the answer.

[Confused-o-Screaming]

I determined that deleting jellyfin.db caused this error in the logs. However, changing library.db.old back to library.db doesn't cause the migration to start again in an attempt to resolve this problem.

The logs show the migration service being initialized then finding 0 migrations for stage coreinitialization before starting as normal

Edit: Looks like scanning all libraries fixed it?

[R0gue_One]

I'm also having this issue, but found that if I click on "Next Up" my partially watched item is there. I did try scanning all libraries from the main dashboard, but that didn't fix it. Any other suggestions? I didn't notice any errors during the upgrade to

[Confused-o-Screaming]

I'm also having this issue, but found that if I click on "Next Up" my partially watched item is there.  I did try scanning all libraries from the main dashboard, but that didn't fix it.  Any other suggestions?  I didn't notice any errors during the upgrade to

I scanned my library after deciding to create a new user to migrate to while keeping the issue user for Symfonium to use. To recreate exactly what I did, try creating a new user, mark a few things as watched, verify that continue watching works then try scanning the library. I ran the scan from the issue user account and didn't exit that dashboard until the scan was finished 

Hopefully that works and it wasnt just a fluke for me. Outside of trying the migration a bunch of times, this is all I "Tried" and accidentally fixed it

[alleycat]

I'm also having this issue, but found that if I click on "Next Up" my partially watched item is there.  I did try scanning all libraries from the main dashboard, but that didn't fix it.  Any other suggestions?  I didn't notice any errors during the upgrade to

I'm having the exact same issue with Continue Watching. I've been on the 10.11.0 release now for a few days. No problem with Continue Watching right after the upgrade. Once I watched the existing items in the Continue Watching section of the Home page, I started having a problem with "new" views not showing up in that section of the Home page. Like others stated my partially watched videos are found in the libraries and can continue watching from there. This seems to be happening to my user account (admin) but my two "test" users, it works fine. I tried the above suggestions with no luck. Nothing in the log relates to the issue.
Anyone else with this problem and how did you proceed? This issue is marked "solved" be didn't work for me. Should I start a new thread?

[R0gue_One]

Unfortunately creating a new user did not work. Steps I took:

1. Created a new admin user
2. Logged in, and started watching three separate movies and two TV shows.
3. All items appeared in "Continue Watching" section.
4. Went to Dashboard, and scanned all libraries.
5. Logged out of original user account with user
6. Logged back in, no Continue Watching items. Next Up only works for TV shows, not Movies.
7. Started two new movies, skipped ahead, backed out, and do not appear under Continue Watching.
8. Manually going to the Movie and playing will resume at last playback.

At a loss here what is going on and why it's affecting specific user accounts and not all.

[Dreizack]

Hello,

I’m experiencing the same issue. Since the 10.11.0 update, the “Continue Watching” feature has stopped working. I’ve tried everything I could think of — turning the feature off and on again, creating a new user profile, running a full library scan, and more — but nothing helped. I have no idea what’s causing the problem or how to fix it, so I’m kindly asking for assistance with this issue.

Thank you in advance for your help.

[icassassin]

I'm also having this problem since upgrading from 10.10.7. I'm running this on an Ubuntu 24.04 install, native binaries.

When I first upgraded via apt, migration failed due to 'libjemalloc' not being on my system at the time. I installed that and restarted Jellyfin and things were working OK. I did a full library scan and that went through without a hitch. But the only things showing up in 'Continue Watching' were the TV shows that were there before the upgrade. No movies show up, despite some having been in 'Continue Watching' before the upgrade. Subsequent watches of any movie or TV show do not add into 'Continue Watching'. Watching or marking watched a TV show in the 'Continue Watching' header will remove it.

I also tried remigrating but that doesn't seem to be working. Whenever I rename 'library.db.old' to 'library.db' and remove 'jellyfin.db' I see this in the logs:

Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: __EFMigrationsHistory'.
  at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
  at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext()
  at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext()
  at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
  at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
  at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
  at Microsoft.Data.Sqlite.SqliteCommand.ExecuteNonQuery()
  at System.Data.Common.DbCommand.ExecuteNonQueryAsync(CancellationToken cancellationToken)

and Jellyfin does not start. I've tried toying with renaming 'migrating.xml.backup' to 'migrating.xml' in settings but still the same thing. I'm not sure if I'm supposed to do something else to get Jellyfin to try the migration again and I'm just doing it wrong.

[alleycat]

I'm also having this problem since upgrading from 10.10.7. I'm running this on an Ubuntu 24.04 install, native binaries.

When I first upgraded via apt, migration failed due to 'libjemalloc' not being on my system at the time. I installed that and restarted Jellyfin and things were working OK. I did a full library scan and that went through without a hitch. But the only things showing up in 'Continue Watching' were the TV shows that were there before the upgrade. No movies show up, despite some having been in 'Continue Watching' before the upgrade. Subsequent watches of any movie or TV show do not add into 'Continue Watching'. Watching or marking watched a TV show in the 'Continue Watching' header will remove it.

This is the exact scenario that happened to me.  The only fix for me was to create a new admin user and proceed from there. I left the old admin with all my watched and continue history in place in case a "fix" comes down...

[icassassin]

I'm also having this problem since upgrading from 10.10.7. I'm running this on an Ubuntu 24.04 install, native binaries.

When I first upgraded via apt, migration failed due to 'libjemalloc' not being on my system at the time. I installed that and restarted Jellyfin and things were working OK. I did a full library scan and that went through without a hitch. But the only things showing up in 'Continue Watching' were the TV shows that were there before the upgrade. No movies show up, despite some having been in 'Continue Watching' before the upgrade. Subsequent watches of any movie or TV show do not add into 'Continue Watching'. Watching or marking watched a TV show in the 'Continue Watching' header will remove it.

This is the exact scenario that happened to me.  The only fix for me was to create a new admin user and proceed from there. I left the old admin with all my watched and continue history in place in case a "fix" comes down...

So I've done a little more experimentation here:
I had some backups of my Jellyfin data prior to my upgrade attempt. So I replaced 'jellyfin.db' and 'library.db' with day old versions of those files (not any generated by the upgrade process). I also renamed 'migrating.xml.backup' to 'migrating.xml' in '/etc/jellyfin' on my system. I restarted Jellyfin and it does properly do the migration again. Maybe the upgrade process does something to 'library.db' that it shouldn't be doing before making the backup. I dunno.

Migration seemed to go without a hitch. Server started; had to re-login with my account. Did a full library scan.

And 'Continue Watching' now seems to be working as expected.

alleycat, if you've got another backup of your 'jellyfin.db' and 'library.db' files, you might want to give this a whirl.