Repository navigation
Automations: Run workflow when download is completed #1128
Replies: 7 comments 4 replies
This comment has been hidden.
This comment has been hidden.
|
It could have been added as one of the Actions - see #1192 |
|
As a more concrete example of where the inability to run automations with qui on torrent "state" change leads to errors. Currently the minimum automation interval is 1 minute per rule.
A similar discussion proposal here Ability to run automations on torrent add The example in the docs Speed Limit Private Trackers would not work as intended because the limit would be un-applied for potentially a minute, causing problems with certain trackers Both proposals target the same thing, ability to run a automation on torrent add / complete. Or in general on a "state" change. This would also allow the ability to run an automation once. Added here instead of a new discussion since this and the other linked discussion are similar. |
|
+1, would love to see event-driven automations (eg. state changes, torrent add to trigger reannounce watch or quickly set share limits for pubs, search/scan completion, cross-seed injection etc.) instead of running them every X. In my case, most automations are only useful within a specific time window, vast majority of time nothing happens. |
Agent BriefCategory: enhancement Related: #1192 and #1520 ask for the same event-driven triggering. Current behavior: Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: The trigger model is a product decision. Which torrent states become triggers, whether one rule may carry both a trigger and an interval, and how qui detects a transition that qBittorrent never pushes all shape the automations schema and the rule editor before any code is written. Feature scope is a maintainer call. |
|
Could this be done by adding an API endpoint to trigger automations? That way you could use a script with a curl that gets fired with the existing |
Uh oh!
There was an error while loading. Please reload this page.
If users could define/specify workflow automations to execute when a download is completed, it would improve the user experience & allow for those workflows to be run less frequently across the entire client (potentially improving performance on resource-constrained hosts).
This would allow for things like quickly applying share limits to torrents (such as public ones, or to ensure less congestion/io load) rather than waiting for the next execution interval. I have not specifically recorded it, but complex workflow rules on large numbers of torrents could result in high CPU load, so executing those on very short intervals may be problematic for some users.
The code used for executing cross-seed searches could possibly be leveraged to also include workflow executions for quicker implementation.
All reactions