Mass "addedAt" metadata value change breaking Recently Added

Server Version#: 1.13.8.5395
Player Version#: N/A

Sometime this morning, the “updatedAt” value for the majority of my video files changed to a value from today. I’ve had this happen with a small number of files once or twice in the past where the “updatedAt” value showed a time in the future, and I was able to directly edit the sqlite DB to set the “updatedAt” value on the affected files to match the “addedAt” value, which worked pretty well to get them “unstuck” from my Recently Added list. But that was when I had a half dozen or so affected files, currently I’m dealing with hundreds of affected files and instead of showing a value in the future, they’re showing a value from earlier today.

What events would cause the “updatedAt” value to change inside the Plex XML metadata? Hopefully an answer to that question that will let me figure out why this occurred and how I can prevent it in the future.

For what it’s worth:

  • I was not using Plex (or even the computer that PMS runs on) when the mass updatedAt change occurred.
  • As far as I can tell, my NAS didn’t lose connection to the host running PMS – no power or network outages, etc (plus, my NAS losing connection or its volume getting unmounted has never caused problems in the past).
  • All of the modified times/mtimes on my media files have stayed the same. I’m seeing files with mtimes from 2015 showing “updatedAt” values from 2 hours ago.
  • It looks like all poster/cast/etc metadata was lost for the affected files. The media agents correctly replaced them but when I first noticed something was wrong, a lot of the affected files still didn’t have posters and were still getting populated.
  • Watched/Unwatched status does appear to have been retained on the affected files.
  • My files were not affected uniformly across libraries: about 90% of files in my Shows library were affected, about 80% of my Movies, about 50% of my Documentaries, about 40% of my Shorts, and 0% of my Music.
  • To reiterate the above point: In each affected library, there were at least some files that were NOT affected despite being in the same top-level folder on my NAS (i.e. while 80% of my Movies now show as Recently Added, 20% DO NOT show as recently added and retain their correct “updatedAt” value despite living in the same /Volumes/Movies directory as the affected files). This would all make more sense to me if 100% of the files in a library were affected but a seemingly random subset of files within a library being affected seems really weird.

I’m running the newest stable PMS on MacOS High Sierra. My media lives on a Synology NAS that is volume mounted to the Mac. This has all been working fine for years…

So, what are the conditions that would cause the “updatedAt” value to change under normal conditions? What would cause “updatedAt” to change en masse? How can I fix this? How can I prevent this from happening again?

UpdatedAt is not addedAt.
Changing updatedAt has no influence on the ‘Recently Added’ hub on your Plex clients.
I’m a bit puzzled by you mixing these two things up.

UpdatedAt is changed to the current date as soon as this item gets re-analyzed or gets it’s metadata refreshed. It is a perfectly normal operation, which may even get performed automatically by Plex server, according to what is activated under
Settings - Server - Scheduled Tasks

You’re right, I apologize. I got “addedAt” and “updatedAt” backwards. Both of those values are showing as earlier today for the affected files. I guess the question I should’ve been asking is:

What would cause a bunch of files that have been in my Plex libraries for months/years and in the exact same location on disk for months/years to suddenly set their addedAt time to today? It’s like it lost track of the majority of the files in most of my libraries, then found them again and re-added them. But it didn’t affect all of the files in the libraries and Plex retained Watched/Unwatched status for the affected files.

Very often if you update a library (or the server does, depending on its ‘Libraries’ settings) and the media file storage is either slow to react (spinning up hard drives takes too long) or the network connection is not 100% reliable, these files may get marked as ‘unavailable’.

If you have now activated the checkbox ‘Empty trash automatically after every scan’
under Settings - Server - Library
these unavailable files will get removed from the library immediately.
On a subsequent library update, these files then get re-added to the library, explaining why the addetAt timestamp is changed.

If your media storage is not 100% local, you must never activate this checkbox!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.