Normal
Without knowing the IMDb+ settings you used, Full Path + Filename of the culprit in question and any other relevant information, it will ALWAYS REMAIN weird, because I can only fix something if I can reproduce the problem or am provided proper log files that allow me to see what is going wrong. I import about 10 movies a week on different names/methods to ensure IMDb+ is still working, aside from IMDb+ users reporting issues to me on the IMDb+ forum section. There are no issues as far as I'm aware with v4.9.30, but I'll be happy to fix if there are. More then likely you have something else happening. Enable display of scaper-script name setting, more then likely IMDb+, IMDb (default) and TMDb were all offering you the 3 results you saw due to the import settings you are using. Ideally you disable all the scraper scripts you do not use/need to prevent false positives. Without enabling the option to see the scraper-script name responsible for the result, it can indeed look confusing.
Without knowing the IMDb+ settings you used, Full Path + Filename of the culprit in question and any other relevant information, it will ALWAYS REMAIN weird, because I can only fix something if I can reproduce the problem or am provided proper log files that allow me to see what is going wrong.
I import about 10 movies a week on different names/methods to ensure IMDb+ is still working, aside from IMDb+ users reporting issues to me on the IMDb+ forum section. There are no issues as far as I'm aware with v4.9.30, but I'll be happy to fix if there are.
More then likely you have something else happening. Enable display of scaper-script name setting, more then likely IMDb+, IMDb (default) and TMDb were all offering you the 3 results you saw due to the import settings you are using. Ideally you disable all the scraper scripts you do not use/need to prevent false positives.
Without enabling the option to see the scraper-script name responsible for the result, it can indeed look confusing.