Run external program on "torrent stop" (usecase: is if program is trying to rename/move files, it can be successful only if files are not in use by qbit) #11425

New issue

Open

opened 2026-02-21 21:29:55 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 21:29:55 -05:00

Owner

Originally created by @abegreen on GitHub (Dec 15, 2020).

Suggestion:

With current "run program" feature we can only execute program when torrent finishes downloading, but since it is still seeding until ratio goal is reached, we need an option to run program on "torrent stop".

One practical reason for this suggestion is if program is trying to rename/move files, it can be successful only if files are not in use by qbit.

Originally created by @abegreen on GitHub (Dec 15, 2020). Suggestion: With current "run program" feature we can only execute program when torrent finishes downloading, but since it is still seeding until ratio goal is reached, we need an option to run program on "torrent stop". One practical reason for this suggestion is if program is trying to rename/move files, it can be successful only if files are not in use by qbit.

deekerman added the

Feature request

Core

Triggers

labels

2026-02-21 21:29:55 -05:00

deekerman commented

2026-02-21 21:30:00 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 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 24, 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.)**

deekerman commented

2026-02-21 21:30:00 -05:00

Author

Owner

@abegreen commented on GitHub (Sep 29, 2025):

I am back 5 years later. I still think that external program should run after torrent is completed and stopped.

Running it immediately after download finishes, means that the torrent is in seeding state and external program cannot make changes to files while they are being used.

In old utorrent, there were numbers (values) for every torrent state. Completed & Stopped had value "11", so external script ran on every change of state, but was programmable to only execute if TorrentState='11'.

In BiglyBT, we can add a tag that will run the external script, with condition to add it (tag) when torrent is Completed & Stopped.

I've been scrolling through Qbit settings and it came to my mind that the trigger that we need to run script is when seeding limit is reached. We need an option to stop+run script. It's been there all this time.

To me, this feature is essential, and the lack of it is illogical. I need this or I can't make use of Qbit client.

@abegreen commented on GitHub (Sep 29, 2025): I am back 5 years later. I still think that external program should run after torrent is completed and stopped. Running it immediately after download finishes, means that the torrent is in seeding state and external program cannot make changes to files while they are being used. In old utorrent, there were numbers (values) for every torrent state. Completed & Stopped had value "11", so external script ran on every change of state, but was programmable to only execute if TorrentState='11'. In BiglyBT, we can add a tag that will run the external script, with condition to add it (tag) when torrent is Completed & Stopped. I've been scrolling through Qbit settings and it came to my mind that the trigger that we need to run script is when seeding limit is reached. We need an option to stop+run script. It's been there all this time. To me, this feature is essential, and the lack of it is illogical. I need this or I can't make use of Qbit client.