Continue Watching shows different content in native apps vs web UI

Hi all, having a weird one and hoping someone else has seen this.

My Continue Watching row is showing completely different content depending on how I access Plex:

  • Plex Web (PC browser, local) → correct, shows everything including recently watched shows
  • app.plex.tv (mobile browser) → also correct, matches PC
  • Plex Android app → wrong, missing recently watched items entirely
  • Nvidia Shield Plex app → also wrong, same missing items

So the web UI is fine everywhere, but native apps on multiple devices are all showing a different (incorrect) Continue Watching list. The items aren’t just out of order — they’re completely absent. For example, The Traitors (US) S3E5 which I watched this morning is showing correctly in the web UI but doesn’t appear anywhere in the native app Continue Watching list, even when expanding the full list (which has hundreds of entries).

What I’ve tried:

  • Cleared cache and data on Android app, signed back in — no change
  • Optimized database and cleaned bundles on the server
  • Restarted Plex Media Server
  • Confirmed same account and profile on all clients (only one profile)

Setup:

  • PMS version: 1.43.2.10687
  • Android app: older version (kept deliberately for features)
  • Nvidia Shield app: current version
  • Single user, no Plex Pass

The fact that it affects two different native app versions but not the web UI suggests the native apps are fetching Continue Watching differently to the web UI, and something has gone wrong on that code path. Has anyone seen this or know of a fix?

Have you confirmed that every app has the same libraries pinned/favorited?
Which libraries are pinned is reflected in the Continue Watching hub.
If a library is not pinned, its content will not appear on the Home page.

Yes thankyou, nothing has changed in the libraries pinned etc. Its all a single library anyway. It started 2 days ago with nothing changed. Same server for roughly 4 years and never had this happen. Thanks again

Is it possible that some of the libraries are currently using outdated (“legacy”) metadata agents? These may be treated differently by newer client app versions.

You should investigate if you can update the agent selection on all your libraries to the currently supported agents.