Your logs are full of connection errors to Deluge, if Deluge fails to respond properly (or responds saying it failed to add), Sonarr would try to queue another release.
Looks like we’re talking about two separate issues though:
-
Two actions add releases to the download client at the same time (RSS and search) - a queue here may prevent it, but it wouldn’t be guaranteed since both could check the queue, see no conflicts and both try to queue because adding to the queue is the last thing Sonarr does after checking all the results
-
Deluge responds with an error/appears to fail to receive the torrent so Sonarr attempts another release, because the request failed Sonarr doesn’t apply a label to the release or track it.
With 1 there isn’t a lot we can do, we do track downloads in a queue of the download client and this is a fringe case that could happen, but wouldn’t happen often. For 2 this is a problem with Deluge, not something we can fix, if Deluge send a failed response/doesn’t respond properly Sonarr accepts that as fact, it won’t check to see if its incorrect, it will try a different release.