
Well enter XEM which creates a map for Sonarr to look at. Typical Issue: Scene numbering does not match TVDb numbering so Sonarr doesn't work. If the episode wasn't there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it. In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing hammer the indexer with useless requests. In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.
Sonarr setup torrent download client Offline#
There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would.

As long as your indexer supports paging and it hasn't been too long Sonarr will be able to process the releases it would have missed and avoid you needing to perform a search for the missed episodes.


If you understand this, you will realize that it only covers the future though. This lets Sonarr cover a library of any size with just 24-100 queries per day (RSS interval of 15-60 minutes). Instead, it fairly frequently queries your indexers and trackers for all the newly posted episodes/newly uploaded releases, then compares that with its list of episodes that are missing or need to be upgraded.
