[FEATURE] Different tolerance depending on download progress #102

New Issue

giteasync · 2025-10-09T16:58:24-05:00

giteasync commented

2025-10-09 16:58:24 -05:00

Originally created by @lucasvianav on GitHub.

What would you like to see implemented next?

Hey, thank you for your work on this! I'd love to have the ability to set different tolerance for torrents depending on download progress. For example, my ideal setup would be something like:

Remove torrents stalled/slow for 24 hours if downloaded less than 1%
Remove torrents stalled/slow for 1 week if downloaded less than 50%
Remove torrents stalled/slow for 2 weeks if downloaded less than 90%
Remove torrents stalled/slow for 1 month if downloaded over 90%

Currently I have a few torrents not that easy to find sitting at 99.8% progress with the hope of someone who has that last bit coming online, and wouldn't like to delete them too soon.

I imagine this could be done with different number of strikes until deletion for each percentage range.

Originally created by @lucasvianav on GitHub. ### What would you like to see implemented next? Hey, thank you for your work on this! I'd love to have the ability to set different tolerance for torrents depending on download progress. For example, my ideal setup would be something like: 1. Remove torrents stalled/slow for 24 hours if downloaded less than 1% 2. Remove torrents stalled/slow for 1 week if downloaded less than 50% 3. Remove torrents stalled/slow for 2 weeks if downloaded less than 90% 4. Remove torrents stalled/slow for 1 month if downloaded over 90% Currently I have a few torrents not that easy to find sitting at 99.8% progress with the hope of someone who has that last bit coming online, and wouldn't like to delete them too soon. I imagine this could be done with different number of strikes until deletion for each percentage range.

giteasync added the

enhancement

planned

labels 2025-10-09 16:58:24 -05:00

giteasync commented

2025-10-09 16:58:25 -05:00

@Flaminel commented on GitHub:

Hi! I'll think about this and get back to you when I have an idea on how to proceed.

@Flaminel commented on GitHub: Hi! I'll think about this and get back to you when I have an idea on how to proceed.

giteasync commented

2025-10-09 16:58:26 -05:00

@Flaminel commented on GitHub:

@lucasvianav @hacshacdgacs are you available in the next days to test this feature?

@Flaminel commented on GitHub: @lucasvianav @hacshacdgacs are you available in the next days to test this feature?

giteasync commented

2025-10-09 16:58:26 -05:00

@hacshacdgacs commented on GitHub:

Adding a plus one for this since progress conditions could be good for private trackers (since there'sa threshold before they become hit&runs)

@hacshacdgacs commented on GitHub: Adding a plus one for this since progress conditions could be good for private trackers (since there'sa threshold before they become hit&runs)

giteasync commented

2025-10-09 16:58:26 -05:00

@lucasvianav commented on GitHub:

hey! I don't have Cleanuparr currently set up, but should have time to do it in the weekend

@lucasvianav commented on GitHub: hey! I don't have Cleanuparr currently set up, but should have time to do it in the weekend

giteasync referenced this issue

2025-10-09 16:59:08 -05:00

[FEATURE] Ignore qBitTorrent Queue #125

giteasync referenced this issue

2025-10-09 17:00:36 -05:00

[PR #102] [MERGED] Fix qBit queued items being processed #254

Sign in to join this conversation.