starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Delay between searches for less hammering on indexer #9247

New issue

Closed

opened 2026-02-20 00:12:03 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 00:12:03 -05:00

Owner

Originally created by @blixten85 on GitHub (Aug 10, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

A default delay between searches would be very handy so the indexers doesn’t temporarily ban the ip from searches.
30 seconds as a default and the option to choose whatever we want but with a hardcoded minimum that works well with the trackers.

Describe the solution you'd like

Read above

Describe alternatives you've considered

Read above

Anything else?

Read above

Originally created by @blixten85 on GitHub (Aug 10, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Is your feature request related to a problem? Please describe A default delay between searches would be very handy so the indexers doesn’t temporarily ban the ip from searches. 30 seconds as a default and the option to choose whatever we want but with a hardcoded minimum that works well with the trackers. ### Describe the solution you'd like Read above ### Describe alternatives you've considered Read above ### Anything else? Read above

deekerman

2026-02-20 00:12:03 -05:00

closed this issue
added the
Type: Support.
label

deekerman commented

2026-02-20 00:12:05 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Aug 10, 2025):

Given that Radarr generally doesn’t perform auto-searching, there’s no need for a feature that’s entirely user-caused and, therefore, entirely user-avoidable. You - the user are yourself or configuring a software to trigger searches. No plans for this.

Prowlarr/Jackett captures the 429 retry times from various sites and provides that information back to Radarr. Sites should respond to search request limits with appropriate 429 + retry after times.

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

@bakerboy448 commented on GitHub (Aug 10, 2025): Given that Radarr generally doesn’t perform auto-searching, there’s no need for a feature that’s entirely user-caused and, therefore, entirely user-avoidable. You - the user are yourself or configuring a software to trigger searches. No plans for this. Prowlarr/Jackett captures the 429 retry times from various sites and provides that information back to Radarr. Sites should respond to search request limits with appropriate 429 + retry after times. For support and inquiries, please use our [Discord](http://radarr.video/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

deekerman commented

2026-02-20 00:12:05 -05:00

Author

Owner

@blixten85 commented on GitHub (Aug 11, 2025):

Given that Radarr generally doesn’t perform auto-searching, there’s no need for a feature that’s entirely user-caused and, therefore, entirely user-avoidable. You - the user are yourself or configuring a software to trigger searches. No plans for this.

Prowlarr/Jackett captures the 429 retry times from various sites and provides that information back to Radarr. Sites should respond to search request limits with appropriate 429 + retry after times.

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

What? I’m responsible? If I search for all under missing or cutoff, it will search for all of the things in there and there is nothing I can do to affect this timespan between searches for each items in this queue.
Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually?

Your answer is very provocative and ignorant bakerboy.

@blixten85 commented on GitHub (Aug 11, 2025): > Given that Radarr generally doesn’t perform auto-searching, there’s no need for a feature that’s entirely user-caused and, therefore, entirely user-avoidable. You - the user are yourself or configuring a software to trigger searches. No plans for this. > > Prowlarr/Jackett captures the 429 retry times from various sites and provides that information back to Radarr. Sites should respond to search request limits with appropriate 429 + retry after times. > > For support and inquiries, please use our [Discord](http://radarr.video/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you. What? I’m responsible? If I search for all under missing or cutoff, it will search for all of the things in there and there is nothing I can do to affect this timespan between searches for each items in this queue. Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually? Your answer is very provocative and ignorant bakerboy.

deekerman commented

2026-02-20 00:12:05 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Aug 11, 2025):

Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually?

Correct - covered in the documentation. Use upgradinatorr or similar to sanely do sane batch searching. There is just about never any reason to do a search all - see FAQ 1

@bakerboy448 commented on GitHub (Aug 11, 2025): > Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually? Correct - covered in the documentation. Use upgradinatorr or similar to sanely do sane batch searching. There is just about never any reason to do a search all - see FAQ 1 For support and inquiries, please use our [Discord](http://radarr.video/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

deekerman commented

2026-02-20 00:12:06 -05:00

Author

Owner

@blixten85 commented on GitHub (Aug 11, 2025):

Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually?

Correct - covered in the documentation. Use upgradinatorr or similar to sanely do sane batch searching. There is just about never any reason to do a search all - see FAQ 1

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

So I have to use a whole other program just because you don’t want to add a 30 seconds delay between searches?
Where is the sanity in that?

@blixten85 commented on GitHub (Aug 11, 2025): > > Unless you think it’s my fault for using the ”search all” function in missing and cutoff sections when I clearly could have searched for one item at a time manually? > > Correct - covered in the documentation. Use upgradinatorr or similar to sanely do sane batch searching. There is just about never any reason to do a search all - see FAQ 1 > > For support and inquiries, please use our [Discord](http://radarr.video/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you. So I have to use a whole other program just because you don’t want to add a 30 seconds delay between searches? Where is the sanity in that?