Quality upgrades to existing titles are showing in Recently Added

I use Sonarr and Radarr. Recently, all quality upgrades to existing titles are showing up in Recently Added. This didn’t use to happen unless I manually deleted a file before adding the new one.

I have made some recent changes to my setup, but I’m not sure where they would cause this. PMS, Sonarr, and Radarr have not moved, but the storage and downloads locations have. PMS lives on its own physical Windows 10 machine and pulls media from a FreeNAS server (running as a VM in ESXi 7 on an R730xd, though that’s probably irrelevant here) over the LAN. Sonarr and Radarr live on yet another separate Windows machine and dl to their own scratch pool on the FreeNAS server and then move completed files to the media pool on the same server and notify Plex.

Until the recent addition of the FreeNAS server, I had my movies library as a local Windows storage pool in the machine hosting PMS. The TV shows library was on a Synology NAS. Sonarr and Radarr would dL to to their own downloads folders on the same device as their respective associated Plex libraries (Synology NAS TV, Win 10 storage pool Movies).

I found an older closed post where someone had the opposite problem - they wanted this behavior - and it was mentioned that updates over the wire behave differently than on the local machine. I don’t recall this behavior with TV shows upgrading on the NAS previously though.

Any ideas on how to stop this? I know I can manually edit the database, but that is far from ideal for this regularly recurring situation. I’m also not at all experienced in scripting, so aside from using someone else’s, that’s not a great option for me either.

Thanks in advance!

Woah, there’s an echo in here! Somebody else posted almost exactly the same thing at the same time.

This also sounds like it might be the same bug I was experiencing. If so, it’s a known issue and a fix is on the way.

Whoa, crazy. And I guess I missed your post as well. Thanks for letting both of us (and everyone else reading this) know it’s a known issue with a fix in the works. It’s always harder to troubleshoot when multiple changes have been made at the same time and I would have pulled my hair out on this one.

In addition to moving the storage and scratch locations, I left out the part about also having moved PMS from a physical Windows installation to an Ubuntu server vm, to a Windows vm, and ultimately back to the physical Windows installation where it started. Three lefts, if you will. Sometimes they make a right, kind of. It’s nice to know despite all the shifting around, this one wasn’t on me. Thank you!

1 Like

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