Removed notification connection is still in use

[aso824]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Current Behavior

I was tired of messages on Telegram channel about indexer failure (un-checking all options didn't helped), so I removed Telegram connection. And I still get sometimes a message about failure. Tried restarting Prowlarr multiple times, including upgrading to newest version - problem still occurs.

Expected Behavior

No more messages after removing a connection for Notifications.

Steps To Reproduce

1. Add Telegram connection
2. Remove it

Environment

- OS: Debian 12
- Prowlarr: 1.17.2.4511
- Docker Install: -
- Using Reverse Proxy: -
- Browser: not related

What branch are you running?

Master

Trace Logs?

There is no trace logs because nothing crashes.

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

• 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.

[github-actions]

👋 @aso824, in order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

[mynameisbogdan]

If the connection is removed like you said, there's nothing that Prowlarr can do anymore since the app is not using a form of delayed sending. I suspected either Telegram might have a small delay or you might have another instance that you forgot about?

Either way, without any form of trace logs to confirm your affirmation I'm going to close this.