Repository navigation
Ability to target a specific qBittorrent instance in cross-instance automation conditions #3134
lardbinvalence
started this conversation in
Feature Requests, Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Feature request
Is your feature request related to a problem?
QUI supports connecting to and managing multiple qBittorrent instances. In the automation query builder, the existing cross-instance conditions include:
Exists on Other InstanceSeeding on Other InstanceThese conditions only return whether a matching torrent exists or is seeding on any other active qBittorrent instance. There is currently no way to specify which particular instance should be checked.
I have three qBittorrent instances:
My intended workflow is to keep long-term copies on my home server and remove torrents from a remote seedbox once the content is confirmed to exist on the home server.
The current
Seeding on Other Instancecondition is too broad for this use case. For example, the same torrent may exist on both remote seedboxes, but not on my home server. The condition could still evaluate as true because the torrent exists on another instance, causing the remote copy to be deleted before the home-server copy has been verified.This is particularly important for delete automations, because QUI evaluates automations in sort order and the first matching delete rule wins.
Proposed solution
Add instance-aware versions of the existing cross-instance conditions, allowing the user to select a specific configured qBittorrent instance.
For example:
Exists on InstanceSeeding on InstanceDoes Not Exist on InstanceIs Not Seeding on InstanceWhen one of these conditions is selected, the value should be a dropdown containing the configured qBittorrent instance names.
Example:
All reactions