Search attempt says no API hits available but UI says otherwise

[brianjmurrell]

I did set the log level to debug and restart but nothing more useful than the basic log message was added. The log message is:

Not using [redacted] because all 25 allowed API hits were already made. The next API hit should be possible at 2025-12-14T17:47:14Z

Yet when I look at the indexers page in the UI it says that I have only used 15/25 API hits.

I am happy to provide more information if needed but increasing logs to debug didn't seem to add any more information unfortunately and there was no more/other information in the log about that indexer.

[theotherp]

It's hard to precisely detect API limits, especially when the indexer doesn't return the current values in their response.

You can ask the indexer admins when the limits are reset and post that here.

Apart from that you can set the log file level to debug and enable the logging marker for API limits. You need to display advanced settings for this. Then create debug infos and post the file here.

[brianjmurrell]

It seems that nzbhydra2 is not even trying to do a search at the indexer though because (according to the log entry) it thinks the API limit has been reached. But the UI says otherwise.

So why is there a disconnect?

[theotherp]

I don't know. Post the debug infos.