Repository navigation
Later retrying of potential cross-seed that is currently downloading #1227
Replies: 2 comments 6 replies
Agent BriefCategory: enhancement Current behavior: Desired behavior: Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: This needs product decisions before code: whether qui should persist third-party torrent payloads at all, whether the parking hangs off |
|
Related to this issue, there is a gap between sonarr/radarr accepting a release and qBittorrent showing the torrent. If a check comes in this time, qui returns 404 and autobrr rejects the release. This occurs often with new TV episodes, where trackers announce the same release in the same second. Example below: The next possible match would be then using RSS, which is usually set up to running every 30 minutes which misses most of the first hour seeding. Possible solution would be for qui to return 202 if an *arr grabbed a release with the same name and size in the last minutes. |
Uh oh!
There was an error while loading. Please reload this page.
At the moment, Qui responds with
202 Acceptedfor matching torrent that is still downloading, letting the external process know to retry later. This can be further improved similar to the original cross-seed:Basically the process would be:
/api/cross-seed/webhook/checkendpoint202or similarAll reactions