Allow send email/execute program when errors #14264

New issue

Open

opened 2026-02-22 00:52:03 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 00:52:03 -05:00

Owner

Originally created by @simonbcn on GitHub (Jan 25, 2023).

Suggestion

Currently qBittorrent allows you to send an email/run a program when a torrent has been downloaded or run a program when a torrent is added.
But it does not allow to do the same when an error occurs: disk full, error in a torrent (of whatever type), missing files, etc. when I think this is a really useful use of notifications, especially when running without GUI.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @simonbcn on GitHub (Jan 25, 2023). ### Suggestion Currently qBittorrent allows you to send an email/run a program when a torrent has been downloaded or run a program when a torrent is added. But it does not allow to do the same when an error occurs: disk full, error in a torrent (of whatever type), missing files, etc. when I think this is a really useful use of notifications, especially when running without GUI. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Triggers

labels

2026-02-22 00:52:03 -05:00

deekerman commented

2026-02-22 00:52:09 -05:00

Author

Owner

@RivenSkaye commented on GitHub (Jun 11, 2023):

@luzpaz may I ask why you're posting on 11 issues (so far anyway) that they're supposedly related when some of them are different problems entirely?
For example:

#14523 which is about a circumstance in which a succesfully completed download fails to run the specified command.
#17839 is about qBT failing to run a bash script (issue might even be as simple as bash not being on their %PATH%, reading through the thread)
#4820 is about RSS downloads not triggering a command (on successful completion)

None of those are related to running a command or sending an email upon an error and I didn't even check the other issues you commented on

@RivenSkaye commented on GitHub (Jun 11, 2023): @luzpaz may I ask why you're posting on 11 issues (so far anyway) that they're supposedly related when some of them are different problems entirely? For example: - #14523 which is about a circumstance in which a _succesfully completed_ download fails to run the specified command. - #17839 is about qBT failing to run a bash script (issue might even be as simple as `bash` not being on their `%PATH%`, reading through the thread) - #4820 is about RSS downloads not triggering a command (on successful completion) **None** of those are related to running a command or sending an email upon an error and I didn't even check the other issues you commented on

deekerman commented

2026-02-22 00:52:11 -05:00

Author

Owner

@luzpaz commented on GitHub (Jun 11, 2023):

Sorry, I had too many open tabs while trying to triage. I must of missed the email portion on this ticket and thought it was a generic state change that would trigger an external app.

@luzpaz commented on GitHub (Jun 11, 2023): Sorry, I had too many open tabs while trying to triage. I must of missed the `email` portion on this ticket and thought it was a generic state change that would trigger an external app.

deekerman commented

2026-02-22 00:52:13 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**