Huntarr Working On Sonarr, Lidarr, but not Radarr

[BayIsland757]

Very odd... my Huntarr was working well across the three "ARRs" until a few days ago. Reinstalled, checked configurations - and here is remaining issues: System is running in container on a Synology 1821+ NAS. Radarr working properly.

Within Huntarr, Sonarr & Lidarr both appear on dashboard with upgrades and missing media. Radarr (in a +7K movie library) reports zero movies upgradable or missing (which there are plenty). Zero hits on the API in Radarr, although it reports as CONNECTED. On an identical installation a friend owns, his works perfectly. As I mentioned, this appeared to be working properly a few days ago.

Logs report:
2025-12-16 21:24:49
Information
RADARR
=== RADARR cycle finished. No items processed in any instance. ===
2025-12-16
21:24:48
Information
RADARR
🎯 All 0 movies fit in one page, returning them directly
2025-12-16
21:24:48
Information
RADARR
No movies found eligible for upgrade or error retrieving them.
2025-12-16
21:24:47
Information
RADARR
📊 Found 0 total cutoff unmet movies across 1 pages
2025-12-16
21:24:46
Information
RADARR
No missing movies found.
2025-12-16
21:24:46
Information
RADARR
Starting quality cutoff upgrades processing cycle for Radarr.
2025-12-16
21:24:46
Information
RADARR
Retrieving movies eligible for cutoff upgrade...
2025-12-16
21:24:45
Information
RADARR
No missing movies found in Radarr.
2025-12-16
21:24:44
Information
RADARR
Starting missing movies processing cycle for Radarr.

[sleighton]

When you click on Missing in the Radarr GUI Menu, how many movies are there under Wanted and how many under cutoff unmet?

[BayIsland757]

Missing is 341, needing upgrade is 1,652.

The Debug log shows this message at every cycle: 2025-12-16 21:45:36
Warning RADARR Could not load instance settings for Radarr: name 'configured_instances' is not defined

[sleighton]

That log entry means nothing. Everyone gets those, it's a bogus log message.

Take a screen print of the Huntarr -> Apps -> Radarr page as follows;

That should hopefullly give some clues.

[BayIsland757]

Thank you for your help on this!

[BayIsland757]

[BayIsland757]

I think I just found out what was causing it!

I had MONITORED ONLY set to OFF thinking it would also review unmonitored movies... When I turned it back on, it now appears to be working

[sleighton]

Have you recently messed with the reset interval? It doesn't make sense that the next reset date would be 7 days in the future when your reset interval is 4 days. And the active tracked items = 0 implies the interval was just reset.

[BayIsland757]

I have messed recently with reset interval trying to figure out what was wrong.

It is indeed working now... Interesting in the Lidarr and Sonarr, I have the MONITORED ONLY set to off, and they work fine. In the Radarr instance, that made it non-functional.

Here is screen now....

The minute I changed MONITORED ONLY from off to on, the active tracked items populated and it began tracking upgrades and missing items.

Thank you very much for talking me off the ledge.... do you think that switch for Radarr is misconfigured or misinterpreted?

[sleighton]

Very welcome.

I don't believe the switch is broken, it's On for my Radarr and all is working correctly. I'm wondering if your issue was really the reset interval. You have a fairly high missing and upgrade search count. If your sleep duration is low then you are cycling thru your 300~ missing and 1600~ cutoff unmet quickly and once they've been searched it stops searching until the interval resets again.

So if it completes them in 48 hours, nothing happens again until the 96 hour mark is hit and it resets.

[BayIsland757]

You are my hero, regardless. I would not have tested that if for not your help. Can you please explain two things while I have you on the line? What is the use-case for Schedules since you can already set intervals and pause times.... and finally, the reset function (there is one reset for each app, which I suspect means go ahead and search now. What does the higher reset do - other than a collective reset of the timing? (or do I have that wrong?)

I am very thankful for your assistance.

[sleighton]

Schedules were put in because some users wanted the ability to control when Huntarr was polling the ARRs APIs. The schedules allow the user to set time windows where the ARR is active or not.

The reset interval exists to control the media being searched for with the idea being that each media gets searched once and only once during that time window. Each search is random, so as an example, we get the arr's missing list, eliminate the media in the already searched list from it, then pick X items randomly from that list to search. Those that are searched are then added to the already searched list so that they are not picked again. We then sleep for the sleep duration and then repeat.

The above continues until the reset interval is reached, at that point we start over with an empty already searched list and a new end of reset interval datetime.

This works to protect us from being banned by the indexers that the ARRs pass these searches on to. If you are hitting them too hard they ban your IP and stop you from using the service.