Recently Added has lost it's damn mind

Server Version#: 1.43.2.10687
In the last week (I don’t know exactly the date because I don’t monitor it that closely) the “Recently Added TV Shows” is showing every TV Show starting with the very first TV Show I added 10 or more years ago.

This happens across clients and library users (macOS, iOS, Windows).

“Recently Added Movies” is unaffected as is “Continue Watching”.

New Shows that have been grabbed show up at the front of the list. So, it’s not completely broken. For instance, until this evening the first of the list was ‘Camelot’ (don’t judge). Then, I added a new show ‘NewShow’, and as episodes were downloaded and transferred, ‘NewShow’ was in front of ‘Camelot’ with the counter of episodes.

I really don’t want to crack sqllite open to fix this, and I’m not sure where I’d start.

Any insight or suggestions is appreciated.

Are your media files stored inside of the server machine?

If not, what is the status of the checkbox “Empty trash automatically after every scan”?

If the answers to these questions are “no” and “ticked”, then you rather want to

They are attached to the server via 2 raid arrays - so, I think technically yes, they are inside the server. The question is vague.

The checkbox is ‘ticked’. Now it’s unticked. Is this setting not stored in the database? How would this fix the issue?

The efficacy of a db restore is past it’s viability. I think this has been messed up for about a week, and I don’t want to restore from that far back.

I’d really like to understand what happened. It seems like whatever Plex uses to determine what is recently added is not the actual recently added date, but some flag field?

This setting is stored in the ‘Preferences.xml’ file (in your Plex data folder. As to why it would fix the issue, it will prevent PMS from removing an item from your library if the media associated with is unavailable at the time a scan is performed.

When PMS performs a scan, any item which it previously knew about and which is unavailable is marked as “Trash.” If the setting mentioned is enabled, those trash items are removed from the library. When the next scan is performed where they’re available again, they look like newly-added items. Hence the undesired Recently Added hub behavior.

The real question here is why these media items are unavailable at times.

Most often caused by the OS allowing the hard drives to spin down their platters when idle.

There is no Preferences.xml on Windows.
Anyway there is no need to go digging in some obscure configuration file, when the setting is readily available in the server configuration in the web app.
Settings - [server name] - Library - “Empty trash automatically after every scan”

Fair point. But my (rather obvious) point was that it wasn’t stored in the database. And I wasn’t suggesting they go digging into an obscure configuration file. They specifically asked if it was stored in the DB. I answered “no.”

Why harp on it? Why do you take every opportunity you can to tear me down?

I’m not. But I don’t want fals information be present on these forums. It is bad enough elsewhere.

Pretty sure you meant “false.” Since we’re nitpicking every little thing.

I think you should remove everything past comment 3.

Thanks for the info. What you said makes sense. Since movies and tv are on separate arrays my surmise is there was a delay on the TV storage coming online after a recent power outage and Plex then marked all TV as ‘new’. Since all newly added items are correctly showing up at the front of the list I can just let things handle themselves. Knowing the cause is appreciated, I can mitigate this going forward.

Thanks to everyone for the info and help.