# Plex tvdb "The Circus" matching issue

**URL:** <https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539>\
**Category:** Metadata & Adding Files\
**Tags:** server-mac\
**Created:** [January 17, 2021, 10:39pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539 "2021-01-17T22:39:58Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_001](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/john_001/32/279863_2.png) [@John\_001](https://forums.plex.tv/u/John_001)\
**Post date:** [January 17, 2021, 10:39pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/1 "2021-01-17T22:39:58Z")

</div>

Server Version#: 1.21.1.3876  
Player Version#: 1.26.0.1531-92029e9e

I am adding a file titled:  
`The Circus - S06E01 - Raining Chaos {thetvdb-304498} - [720p HDTV 9834055D].mkv`

It was automatically named properly using FileBot.

I have “TVDB” set for metadata in Plex

Plex keeps associating this with **“The Circus (2018)”** and then renaming it. And the proper TV series **“The Circus”** does not show up as an option when attempting to `fix-match`. It obviously does show up on the TVDB website.

Any ideas on how to resolve this? I have done Plex Dance three times to no avail.

Thanks

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 17, 2021, 10:44pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/2 "2021-01-17T22:44:07Z")

</div>

You will probably need to find the ID on the TVDB and do a `fix match` using that

---

<div class="post-metadata">

**Author:** ![John\_001](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/john_001/32/279863_2.png) [@John\_001](https://forums.plex.tv/u/John_001)\
**Post date:** [January 17, 2021, 10:45pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/3 "2021-01-17T22:45:11Z")

</div>

Using `fix match` Can I plug the id in the name field instead of the name?

I already have the id, it’s in the filename.

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 17, 2021, 10:46pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/4 "2021-01-17T22:46:18Z")

</div>

yep, replace the title with the id and (might as well clear the date field)

---

<div class="post-metadata">

**Author:** ![John\_001](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/john_001/32/279863_2.png) [@John\_001](https://forums.plex.tv/u/John_001)\
**Post date:** [January 17, 2021, 10:47pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/5 "2021-01-17T22:47:58Z")

</div>

Thanks I will give that a shot.

In general do you know why the last episode of a series refuses to be matched to TVDB. All of the others in a series will match and have their proper names and series info.

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 17, 2021, 10:49pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/6 "2021-01-17T22:49:58Z")

</div>

The TVDB agent is a bit broken at the moment, apparently due to recent changes at the TVDB

Current solutions are to use the ID or try the new scanner that is currently in preview.

---

<div class="post-metadata">

**Author:** ![John\_001](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/john_001/32/279863_2.png) [@John\_001](https://forums.plex.tv/u/John_001)\
**Post date:** [January 17, 2021, 10:51pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/7 "2021-01-17T22:51:00Z")

</div>

Thanks. Using the id with ` fix-match` worked perfectly. I was unaware of this method.

---

<div class="post-metadata">

**Author:** ![aeonjoey](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/aeonjoey/32/14524_2.png) [@aeonjoey](https://forums.plex.tv/u/aeonjoey)\
**Post date:** [January 25, 2021, 11:09am UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/8 "2021-01-25T11:09:57Z")

</div>

edit: THANK YOU! this worked for me, thanks!

---

<div class="post-metadata">

**Author:** ![Jumbs](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/jumbs/32/11011_2.png) [@Jumbs](https://forums.plex.tv/u/Jumbs)\
**Post date:** [January 25, 2021, 9:13pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/9 "2021-01-25T21:13:04Z")

</div>

Was about to open a ticket, but i saw this.  
I am having similar matching issues, where items are matching lower level matches only, or nothing.

The Blacklist only finds the spinoff Blacklist:Redemption. And all my Japanese shows fail hard too.  
I know about the ID fix, so right now is just a nuisance.

**Does this sound like the same problem? And it is being worked on?**

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 25, 2021, 9:20pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/10 "2021-01-25T21:20:57Z")

</div>

Yes, they are aware.

From what I understand the legacy agent was written to use only the first answer.

They are now considering patching the existing (legacy) agent to consider all the returned results and use that until the new agent is ready.

But when that might happen is anyones guess…

---

<div class="post-metadata">

**Author:** ![Jumbs](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/jumbs/32/11011_2.png) [@Jumbs](https://forums.plex.tv/u/Jumbs)\
**Post date:** [January 25, 2021, 9:38pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/11 "2021-01-25T21:38:43Z")

</div>

So if i follow, they DB was updated, and plex made a new agent to work legacy style with it?  
And this only gets one result, which is often not a good one?

I know its being worked on just want to understand the problem so i can decide what is best for my system

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 25, 2021, 9:49pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/12 "2021-01-25T21:49:05Z")

</div>

The TVDB api changed the order of the results that they return when you do a search.

the api used to return the highest match first, now it does not.

The legacy (current) agent returns the first result, which is now no longer the best match.

There is a new TV Show agent being developed which does not have the issue, but this is currently only available in a preview version of PMS, and is still in development.

So at the moment we need to wait for Plex to patch the current TV agent, and use `fix match` with the ID from the TVDB until then.

---

<div class="post-metadata">

**Author:** ![blim5001](https://avatars.discourse-cdn.com/v4/letter/b/c2a13f/32.png) [@blim5001](https://forums.plex.tv/u/blim5001)\
**Post date:** [January 27, 2021, 7:49pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/13 "2021-01-27T19:49:09Z")

</div>

And it appears that it has been fixed in the PMS just released a few minutes ago.

Refreshed metadata on my test library and the shows that were not matched:  
`Game of Thrones, Better Call Saul and Mr. Robot`  
all matched without any user input,

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [April 27, 2021, 7:49pm UTC](https://forums.plex.tv/t/plex-tvdb-the-circus-matching-issue/679539/14 "2021-04-27T19:49:15Z")

</div>

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