# Wildly wrong Match: Common Side Effects

**URL:** <https://forums.plex.tv/t/wildly-wrong-match-common-side-effects/916185>\
**Category:** Metadata & Adding Files\
**Tags:** metadata\
**Created:** [May 2, 2025, 4:34am UTC](https://forums.plex.tv/t/wildly-wrong-match-common-side-effects/916185 "2025-05-02T04:34:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\
**Post date:** [May 2, 2025, 7:23am UTC](https://forums.plex.tv/t/wildly-wrong-match-common-side-effects/916185/2 "2025-05-02T07:23:14Z")

</div>

Did it appear as a wrong match on your server before?

I think it can be connected to a previous mismatch.  
Which usually happens when truncated files are matched. (Like a file download that was just started, or a video file that is still being decompressed.)  
The result is that there is a bogohash in the database which fits many truncated video files.  
The only cure known to me is a full [Plex dance](https://forums.plex.tv/t/the-plex-dance/197064) with the original mismatched file as well as all subsequently mismatched files.

Of course it could be also an issue in Plex’s metadata storage.  
I will forward this to the team to verify.

---

_[View the full topic](https://forums.plex.tv/t/wildly-wrong-match-common-side-effects/916185)._