Sonarr version (exact version): 3.0.3.688 Mono version (if Sonarr is not running on Windows): 5.20.1.34 OS: Debian Buster Debug logs: https://www.dropbox.com/s/gvdfe97eyn1axif/logs.zip?dl=0 Description of issue: I did a “search for monitored” for one tv show (Arrow) yesterday after creating a release profile. Naturally, it picked up a lot of upgrades. I don’t have issues when the release is using nzb but am receiving this error for three torrents now after their download completes:
It looks like these releases were grabbed and imported at some point, then re-grabbed, which resulted in one check treating it as already imported, but another treats it as grabbed since it hasn’t imported since being grabbed again.
You mean mention, not ping, right? I wasn’t. This was just a continuation on of the other thread so I figured mentioning you so that you’ll get alerted by this new thread.
I don’t get the cause but yes these were imported in the past as seen by the import date in the warning mesaage. And then they got updated because of the new release profile I made. First it tried usenet and it failed, so it regrabbed a torrent release. The torrent completed and came this warning message. Again, the same exact workflow happened to several releases but only theae three releases had the error message.
What is the workaround for now though? How do I get these imported manually?
I’ll see the new thread when I go through the new threads, just as I saw your previous post that you were going to open a new thread, you need to be patient and wait for me to see it and respond.
Because Sonarr already imported that torrent previously, based on files names/release names it re-grabbed the same torrent.
It’s not really an upgrade if it’s the exact same release.
The release was grabbed, then imported, then it was grabbed again and now Sonarr won’t import it because it already imported it, but that was from before it grabbed it again, it shouldn’t allow the previous import to override the need to import it.
Oh ok, got it. So in a sense, this is the way it’s supposed to work. What will you be “fixing” in the next release as you mentioned in your previous post?
Exactly. But from what you’re explaining in your replies, it looks as if you’re considering this behavior as an intentional one. So I’m not entirely sure where you’re stand at, sorry. Is it an issue or is it intentional behavior?