A way to disable a 'warning' or at least dismiss it.. #9173

New issue

Closed

opened 2026-02-20 00:11:08 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 00:11:08 -05:00

Owner

Originally created by @HikariNoKitsune on GitHub (May 12, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Yes. Currently when there is an 'issue' or something, you get a perma notification on the left hand side under 'System', and when you click on 'System' it tells you at the top of the page what the issue is.

Some of these "Issues" most of us frankly do not care about, and is just causing us to have a constant 'Notification' for something we realistically don't care about, and thus just ignore the little yellow/orange dot... meaning that when a REAL issue pops up, it gets ignored because we no longer mentally 'see' that dot when looking at the page...

Describe the solution you'd like

I would like to see some sort of 'x' at the end of the 'issue message' so that it can simply be dismissed if it is something we genuinely do not care about. This would be the 'quickest and simplest' sort of "Fix" that I can think of... but it would be much more preferable to be able to just... turn off the functions of Radarr that we do not want to use nor care about....

I say this with a specific instance in mind. It may not apply to 'all things' but for my specific use case, its super annoying...

Previously, I had Radarr and Sonarr set to remove a torrent/link/whatever from the download client after it has finished importing. However, I've been recently getting into more of the 'private trackers' and such, which require you to seed your files for a minimum amount of time or ratio. Obviously I would like to follow their rules/standards... So I set my client up to remove the torrents themselves after seeding for the required amount of time. When I first implemented this, there was no issue. But now as of a few updates ago, I just have a persistent 'notification' for 'your download client is set to remove torrents! This CAN result in them being removed before Radarr can import them!'... This sort of notification, that is purely just a 'warning'... really shouldn't be persistent and always active.... It should be dismissible, or be able to be turned off....

I am fully aware that it may get removed before Radarr or Sonarr can import the files. But if after THIRTY DAYS it hasn't imported? There's a bigger problem somewhere... But thankfully that's where the yellow/orange 'activity' notifications come in handy :D cause then I can see when there is a problem and can go fix it. This is also where the webhooks and such come in handy, cause i just get messages when something stalls or needs attention... But the 'warnings' about the client deleting a file before it can be imported, or other ones like 'your folder isn't in the recommended path so you may get some quirky behavior' should be dismissible to those who are already aware of those things, and are doing what they're doing for a reason...

Describe alternatives you've considered

There isn't much of an alternative... Its either you let your download client get clogged with hundreds of entries... or you ignore the yellow/orange dot and potentially miss an actual issue that requires attention.

Anything else?

Not really. I apologize if this sounds alittle terse, it is not my intention. Am merely trying to emphasize aspects n what not. Everything the devs and community do is greatly appreciated. Just wanted to toss out some '2 cents' about what is basically just a 'cosmetic' inconvenience lol.. I understand the warnings are there for a reason, but sometimes a user's situation or circumstance requires it to be set up the way that it is... so being able to prevent my messages from blowing up every couple of hours telling me that there's a 'system issue' would be nice lol.

Originally created by @HikariNoKitsune on GitHub (May 12, 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 Yes. Currently when there is an 'issue' or something, you get a perma notification on the left hand side under 'System', and when you click on 'System' it tells you at the top of the page what the issue is. Some of these "Issues" most of us frankly do not care about, and is just causing us to have a constant 'Notification' for something we realistically don't care about, and thus just ignore the little yellow/orange dot... meaning that when a REAL issue pops up, it gets ignored because we no longer mentally 'see' that dot when looking at the page... ### Describe the solution you'd like I would like to see some sort of 'x' at the end of the 'issue message' so that it can simply be dismissed if it is something we genuinely do not care about. This would be the 'quickest and simplest' sort of "Fix" that I can think of... but it would be much more preferable to be able to just... turn off the functions of Radarr that we do not want to use nor care about.... I say this with a specific instance in mind. It may not apply to 'all things' but for my specific use case, its super annoying... Previously, I had Radarr and Sonarr set to remove a torrent/link/whatever from the download client after it has finished importing. However, I've been recently getting into more of the 'private trackers' and such, which require you to seed your files for a minimum amount of time or ratio. Obviously I would like to follow their rules/standards... So I set my client up to remove the torrents themselves after seeding for the required amount of time. When I first implemented this, there was no issue. But now as of a few updates ago, I just have a persistent 'notification' for 'your download client is set to remove torrents! This _CAN_ result in them being removed before Radarr can import them!'... This sort of notification, that is purely just a 'warning'... really shouldn't be persistent and always active.... It should be dismissible, or be able to be turned off.... I am fully aware that it may get removed before Radarr or Sonarr can import the files. But if after THIRTY DAYS it hasn't imported? There's a bigger problem somewhere... But thankfully that's where the yellow/orange 'activity' notifications come in handy :D cause then I can see when there is a problem and can go fix it. This is also where the webhooks and such come in handy, cause i just get messages when something stalls or needs attention... But the 'warnings' about the client deleting a file before it can be imported, or other ones like 'your folder isn't in the recommended path so you may get some quirky behavior' should be dismissible to those who are already aware of those things, and are doing what they're doing for a reason... ### Describe alternatives you've considered There isn't much of an alternative... Its either you let your download client get clogged with hundreds of entries... or you ignore the yellow/orange dot and potentially miss an actual issue that requires attention. ### Anything else? Not really. I apologize if this sounds alittle terse, it is not my intention. Am merely trying to emphasize aspects n what not. Everything the devs and community do is greatly appreciated. Just wanted to toss out some '2 cents' about what is basically just a 'cosmetic' inconvenience lol.. I understand the warnings are there for a reason, but sometimes a user's situation or circumstance requires it to be set up the way that it is... so being able to prevent my messages from blowing up every couple of hours telling me that there's a 'system issue' would be nice lol.

deekerman

2026-02-20 00:11:08 -05:00

closed this issue
added the
Type: Feature Request

Type: Duplicate
labels

deekerman commented

2026-02-20 00:11:09 -05:00

Author

Owner

@bakerboy448 commented on GitHub (May 12, 2025):

So I set my client up to remove the torrents themselves after seeding for the required amount of time.

Not supported by Starr. The healthcheck for this is clear and there is no reason to need to do this at all. The healthcheck is valid and your setup is the issue. Your download client should pause on completion when goals are hit and would be removed. If you permaseed then use a post import category and qbit manage to support that.

For support and inquiries with the remove completed download functionality , 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 (May 12, 2025): > So I set my client up to remove the torrents themselves after seeding for the required amount of time. Not supported by Starr. The healthcheck for this is clear and there is no reason to need to do this at all. The healthcheck is valid and your setup is the issue. Your download client should pause on completion when goals are hit and would be removed. If you permaseed then use a post import category and qbit manage to support that. For support and inquiries with the remove completed download functionality , 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:11:09 -05:00

Author

Owner

@HikariNoKitsune commented on GitHub (May 23, 2025):

I'll pass, thanks. Discord isn't, and should never, be used for Support. It prevents people from being able to search for and resolve issues. And is also why people tend to post 'duplicates' or already 'solved' issues, because its not in a place that someone can just simply 'google search' to find it on their own, hence needing to open a 'pointless ticket' lol.

Plus, what happens when someone in that server is reported for doing 'horrible things'? then the whole server gets taken down, and whatever 'knowledge' was in it... At least with github, it can be archived for future people to still search through long after it ever gets 'taken down'... can't do that with Discord.

@HikariNoKitsune commented on GitHub (May 23, 2025): I'll pass, thanks. Discord isn't, and should never, be used for Support. It prevents people from being able to search for and resolve issues. And is also why people tend to post 'duplicates' or already 'solved' issues, because its not in a place that someone can just simply 'google search' to find it on their own, hence needing to open a 'pointless ticket' lol. Plus, what happens when someone in that server is reported for doing 'horrible things'? then the whole server gets taken down, and whatever 'knowledge' _was_ in it... At least with github, it can be archived for future people to still search through long after it ever gets 'taken down'... can't do that with Discord.

deekerman commented

2026-02-20 00:11:09 -05:00

Author

Owner

@bakerboy448 commented on GitHub (May 23, 2025):

Again, GitHub is not and will likely never be for support. That is the decision from the team.

@bakerboy448 commented on GitHub (May 23, 2025): Again, GitHub is not and will likely never be for support. That is the decision from the team.