An internal hardening change. No behaviour you configure or see has changed.
What changed
Before removing a download directly from qBittorrent, Protectarr asks every configured application to re-read its download client and waits for each to finish. Since v0.9.3 that check was made once per scan and shared by everything the scan looked at.
That included the content probe, which runs after the main detection pass and can hold a scan for its whole budget - two minutes by default. A download the probe flagged could therefore be judged against an application view established minutes earlier.
The per-download queue and history reads were always fresh requests. What was not necessarily fresh was the application's own picture of its download client, which is only current as of the last time it was made to look.
Each detection pass now gets its own check. Nothing carries over between them.
Why not just allow for the delay
The applications re-read their download clients on their own one-minute timer, so in practice the gap would usually have closed itself. That is not a guarantee Protectarr should rely on: it is someone else's schedule, it is configurable, and it forms no part of any promise Protectarr makes. The boundary between the two passes is a structural fact, so that is what the freshness guarantee is built on - not a timer, not a TTL, and not an elapsed-time threshold.
Cost
At most one extra refresh per application per scan, and only when the second pass actually has something that could be removed. A scan with nothing to remove still issues none at all.
In practice it is usually no extra cost: a scan with something to reap defers the probe to the next pass, so both checks only happen when the first pass asked and then declined to act - which is exactly when the second pass most needs its own answer.
Unchanged
- Provisional ownership and how it is stored
- Remembered grab-history owners
- The per-download queue and history checks behind every decision
- The rule that a check which could not be completed protects the download
- Orphan handling and its dwell
- Normal application-aware remediation
No configuration changes. No migration. README screenshots still show v0.9.0; patch releases do not regenerate them.
ghcr.io/irnutsmurt/protectarr:0.9.4