Prowlarr Search with Bad Indexer #1242

New issue

Open

opened 2026-02-20 10:08:55 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 10:08:55 -05:00

Owner

Originally created by @champs777 on GitHub (Oct 31, 2025).

I attest that there is not an existing issue for this?

I have searched the existing open and closed issues

I confirm this is not related to a Cardigann YML Indexer

Current Behavior

If an indexer is down, the entire search fails if this indexer is included.

Expected Behavior

So this is an interesting bug that took me a while to figure out what was happening.

I have an indexer that is live some days and down most. I am guessing they are going away. For the last few months, every time I use the /search, it instantly returns no results. I couldn't figure out what was going on.

Today I finally figured it out. This indexer that is bad is blowing the entire thing up. If I don't include this indexer in the search, or if I disable this indexer, all is good and the search works.

Over the years indexers will go down from time to time. If they are included in the search, and are down, they should just be skipped. It shouldn't abort the search. Honestly, it could abort the search, but at least let us know that it is because "Indexer X is currently down. Please remove this indexer from your search".

I tagged this as a bug, but could be considered a feature request. =)

Thanks again for an amazing product! I love Prowlarr so much!!!

Steps To Reproduce

Validate that an indexer is down.
Perform a search of many indexers and include this one.
You will see that no matter what you type, nothing is returned by the search.

Environment

- OS: Windows 11
- Prowlarr:2.1.5.5216
- Docker Install: N/A
- Using Reverse Proxy:N/A
- Browser: Brave

What branch are you running?

Master

Trace Logs?

prowlarr_debug_logs.txt

I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @champs777 on GitHub (Oct 31, 2025). ### I attest that there is not an existing issue for this? - [x] I have searched the existing open and closed issues ### I attest this is not related to a Cardigann YML Indexer. - [x] I confirm this is not related to a Cardigann YML Indexer ### Current Behavior If an indexer is down, the entire search fails if this indexer is included. ### Expected Behavior So this is an interesting bug that took me a while to figure out what was happening. I have an indexer that is live some days and down most. I am guessing they are going away. For the last few months, every time I use the /search, it instantly returns no results. I couldn't figure out what was going on. Today I finally figured it out. This indexer that is bad is blowing the entire thing up. If I don't include this indexer in the search, or if I disable this indexer, all is good and the search works. Over the years indexers will go down from time to time. If they are included in the search, and are down, they should just be skipped. It shouldn't abort the search. Honestly, it could abort the search, but at least let us know that it is because "Indexer X is currently down. Please remove this indexer from your search". I tagged this as a bug, but could be considered a feature request. =) Thanks again for an amazing product! I love Prowlarr so much!!! ### Steps To Reproduce Validate that an indexer is down. Perform a search of many indexers and include this one. You will see that no matter what you type, nothing is returned by the search. ### Environment ```markdown - OS: Windows 11 - Prowlarr:2.1.5.5216 - Docker Install: N/A - Using Reverse Proxy:N/A - Browser: Brave ``` ### What branch are you running? Master ### Trace Logs? [prowlarr_debug_logs.txt](https://github.com/user-attachments/files/23268532/prowlarr_debug_logs.txt) ### I attest that Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I attest that I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.