yes, i’ve tried all types of recommendations (db repair, updating, restarting, dns updates) nothing consistently produces the same result.
with no configuration changes, it has worked for the last week then yesterday just stopped working again.
my other thread - Plex media agent - intermittently not working
I’m having these issues as well. I thought it was related to me swapping in a new, larger hard drive, but this issue is very much following the symptoms others are reporting.
I am running PMS on a Ubuntu 22.04.5 box. Current version of PMS is 1.41.8.9834. The fix match returns nothing. I rebooted the box and then tried the fix match. I have attached the logs here. I have not tried the DB fix you listed above in the thread. I’d like to know that I’m resolving the issue and not creating more. 
Thanks for your work on this.
Plex Media Server Logs_2025-06-25_09-37-11.zip (4.4 MB)
I don’t think this is a database issue. My database got corrupted for some random reason so I rebuilt Plex from scratch meaning I uninstalled everything and deleted every plex folder I could find. So even after starting from scratch on v.1.41.8.9834-071366d65 I’m still getting the plex agent not matching issues. It usually resolves itself when I reboot my server. I’m running off Windows 11 24H2.
It’s not a DB issue, not a DNS issue (at least not directly). Rolling back versions fixed this for me. The issue, at least for me, seems to have been introduced into PMS.
I rolled backed to this version - 1.41.8.9834
New version beta released 6/26/25 fixes the issue with the Agent. Beta Release
v.1.41.9.9912-371133ff9
https://www.plex.tv/media-server-downloads/?cat=computer&plat=windows#plex-media-server
June 26, 2025
I am having this issue as well. It seems to primarily affect new movies, but has sometimes also affected new tv shows. Rebooting the server sometimes works, other times hasn’t resolved the problem. Selecting other agents (Edit Library → Advanced → [change media agent]) currently fixes the problem instantly, for both manual and auto-matching, and I can switch back to new agents afterwards without losing the correctly matched metadata. However, who knows how long this will continue to work, as Plex plans to drop all support for plugins at some point in the future.
The new agents work perfectly for days to weeks, but this dysfunction keeps recurring irregularly, and lasts for an indeterminate time. While not every reboot of the server system corrects the problem, the problem definitely persists until a server system reboot, whether the next or otherwise.
The server is running on Ubuntu 20.04.6 LTS, kept updated (current plex version 1.41.9.9961-46083195d)
When the problem occurs, it is universal (for the agents it affects) – i.e. all new movies remain unmatchable, regardless of naming, when the movie agent stops working properly. In all cases, tv show names conform to standard naming rules due to automated library software; when the tv show agent stops working, it appears to handle episodes (this turns out to be a false positive, as episodes are named incorrectly and descriptions are missing entirely), but new tv shows remain unmatched and blank.
Edit: It appears that I incorrectly assumed only movie matching was sometimes affected, looking back, it appears that the tv agent was also always dysfunctional, the effects were just camoflaged.
I’m literally just rebooting my server whenever the issue occurs to be honest. I don’t want to install an older version of Plex so I’ll just keep rebooting until the issue is permanently fixed. I’m running off windows 11 24H2 and running the latest beta version (v1.41.9.9912 x64).
Also still experiencing this issue - didn’t realize until I ran ChuckPa/DBRepair tool (huge thanks for this as well) which confirmed database issues after experiencing my docker image filling to 100% during scheduled database optimization.
Edit: also noting that I had to restart my Plex container to update metadata as others have commented, it was failing prior to this after using DBRepair (and likely long before I realized).
Anyone else still having issues matching stuff even on the latest veresion (1.42.1.10060)? I don’t know where to search for solutions. Nothing works besides having to use the legacy agents for now.
What I can tell from the logs is this entry: ERROR - [Req#945b] MetadataAgentPostProcessor: failed to find agent for identifier tv.plex.agents.series
and the same for the movies agent.
As of 1.42.1.10060 im having problem manually matching a show. Can’t get the agent to find it.
Trying to search tt37913531, tmdb-298271 or tvdb-466865.. nothing yields any results. Just can’t seem to find the show at all with the plex agent. But the show exists on all 3 platforms if i go directly to them and search.
I downgraded to 1.42.1.10054 and it works for me again.
I’m still using the version pms-docker:1.41.5.9522-a96edc606 as it seems to be the latest working version.
I don’t see any improvments here so i’m not upgrading.
But still, this seems to be a real issue, and not seeing a fix is kid of sad 
I hope you’ll find the issue and be able to fix it, Plex is a great product, and i’d love to enjoy the new features
Thanks
You should upgrade, just for the vulnerability alone (if you expose it to the Internet)
Try the 1.42.1.10054 version and let me know if the fixes it for you
I am using PMS Version Version 1.42.1.10060
I am still having the issue. I did the work around and will live with the nasty red error telling me to upgrade my libraries.
Please Plex, fix this soon. I do love the platform.
Thank you,
I’m having the exact same issue. I’d say any new items to the server since about ten days ago cannot be matched at all. Including no-brainers like Titanic.
I just tested switching to The Movie Database agent and it instantly updated all of the unscraped movies that have been sitting in my library. Switch back to Plex Movie, added a new movie and no matches are found. Hopefully they address this soon.
Any new comers to this thread please see the following:
With how frequently PMS crashes, its not really required to restart, it’ll do it on its own.
Sounds like a separate issue. Do you already have a separate post around this? I can move this into another post to discuss further? As always, enable debugging, reproduce the issue, and share your PMS logs.
