Duplicate check
Implementation & testing support
What would you like to see implemented next?
Adding the ability to change qbittorrent category after failed import can help tighten up processing rules for private torrents.
Currently *Arr can be configured to change category after successful import. This allows for external management programs (qui/qbit-manage) to process the torrents based on the new category knowing that the *Arr has completed the import process, such as setting limits and removing them after completion.
If Cleanuparr removes the failed import, does not delete the private torrent, and leaves it in the same import category, then a condition exists where the torrent is in the *Arr import category but it is unknown to external management programs if it has been imported/failed yet or not. This prevents writing a rule for cleanup that is tightly coupled with *Arr's import/failed import of the torrent, potentially deleting a torrent that is completed, but was waiting for something manual within *Arr. (I don't have Cleanuparr handle every single failed import message, there are a few that need to stay manual for inspection or need to wait for an external program to complete)
If Cleanuparr can run the failed import processing based on the specified patterns, leave the private torrent behind, and also change the category, then the processing rules can be configured on the new category (same as if the *Arr changed it), and not the the *Arr import category with an ambiguous status.
This could also be added to the Stalled and Slow Download Rules. Anywhere that is given the option to delete or not delete the private torrent could also have the option to change the category if it is not deleted.
Adding a tag is also a viable option, athough not as preferable as a category change. Both options give something to work with to know that Cleanuparr is done with the torrent.
Duplicate check
Implementation & testing support
What would you like to see implemented next?
Adding the ability to change qbittorrent category after failed import can help tighten up processing rules for private torrents.
Currently *Arr can be configured to change category after successful import. This allows for external management programs (qui/qbit-manage) to process the torrents based on the new category knowing that the *Arr has completed the import process, such as setting limits and removing them after completion.
If Cleanuparr removes the failed import, does not delete the private torrent, and leaves it in the same import category, then a condition exists where the torrent is in the *Arr import category but it is unknown to external management programs if it has been imported/failed yet or not. This prevents writing a rule for cleanup that is tightly coupled with *Arr's import/failed import of the torrent, potentially deleting a torrent that is completed, but was waiting for something manual within *Arr. (I don't have Cleanuparr handle every single failed import message, there are a few that need to stay manual for inspection or need to wait for an external program to complete)
If Cleanuparr can run the failed import processing based on the specified patterns, leave the private torrent behind, and also change the category, then the processing rules can be configured on the new category (same as if the *Arr changed it), and not the the *Arr import category with an ambiguous status.
This could also be added to the Stalled and Slow Download Rules. Anywhere that is given the option to delete or not delete the private torrent could also have the option to change the category if it is not deleted.
Adding a tag is also a viable option, athough not as preferable as a category change. Both options give something to work with to know that Cleanuparr is done with the torrent.