Movie Collections not being created with New Plex Agent

So I am running the very latest release 1.20.3.3437 on a Synology NAS and switched all my libraries to the new Plex Movie Agent, re-scanned all libraries, re-analyze them all, updated all the metadata and also set Minimum automatic collection size to 2. I am assuming that just like the old agent, the server would immediately start building categories, except nothing happens. I only have a few manual categories I created long ago showing up in the Categories screen. What am I doing wrong, or is there some manual “Create Collections” process I need to start to make this happen?

Also, I ran several manual scans with the different collection size set to other numbers but nothing seems to make any difference…no categories are created at all.

Could anyone please give me any pointers as to why this is not working?

Depending on how old the library is, simply changing the scanner selection might not be enough. Check this article and see if it helps:

Thank you @beckfield. The libraries are a couple of years old maybe. I’ve seen that page and followed all the instructions down to the letter…still nothing happens. :frowning:

Honestly right now I am seriously pondering just deleting the entire movie library and re-building it from scratch after spending so much time troubleshooting this. 3,000 movies is a lot to scan through but honestly I am so frustrated right now with this.

All you would need to do is “Upgrade Matching”, set the min collection size then “Refresh All Metadata”.

If collections aren’t being created after this is compete then the Collection tag on the movies is likely set to a locked state (this happens automatically if you delete existing collections) and you would have to unlock those fields before it would create the new collections.

Quick update: I’ve done all the things recommended and read about. I ended up creating a new Movies library and the scanner scanned it and created all the Collections correctly. Something doesn’t work right with just the “Upgrade matching” path but I am not sure how to even reproduce a bug like this.

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