Downloads in qBitTorrent not imported

[Kedryn]

I've migrated from Readarr to Bindery, configured it to use my qBitTorrent as a downloader, with the download folder mapped to bindery download.

But, i have nearly 500 downloaded torrents in the book category that are sitting here. Bindery seems to ignore them, and i cant find a way to batch import them.

[vavallee]

The short version: Bindery only imports downloads it grabbed itself, and those ~500 came from Readarr, so it leaves them alone.

When Bindery sends a release to qBittorrent it writes a record tying that specific torrent to the specific book it grabbed it for, and the importer only ever works through those records. Torrents already sitting in your client have no such record, so Bindery has no idea what book they are and doesn't touch them. That's deliberate (it's what stops it from hoovering up unrelated stuff in your client), but it does mean a Readarr migration with a backlog of finished downloads has nothing to latch onto. So they're not erroring, they're just invisible to it.

There's no "batch import what's already in my client" path yet. That's a real gap for migrations and I'm tracking it here: #1292.

One practical angle: since you mapped your qbit download folder into Bindery's download dir, the bulk folder importer planned in that issue would let you point at that folder and bring them in as a batch. The thing to sort out first is that matching runs against books already in your Bindery library, so the authors and books need to exist in Bindery before the files can attach to them. Did your authors come across in the migration, or is the library mostly empty right now? That changes the cleanest path, so let me know.

[vavallee]

Coming back to this much later than I should have. I asked whether your authors had come across and never heard back, so I do not know how your library ended up, but the thing you actually needed did not exist at the time and does now.

Manual Import at /import in the sidebar takes a folder, walks it, and matches everything it can against your catalogue in one pass. Anything it cannot match on its own gets a search box so you can bind it to the right book yourself. For a few hundred Readarr era torrents sitting in a download folder that is the tool, rather than adding them one at a time.

Two things that matter for your case specifically. Bindery has to be able to read the path your torrent client reports, so if the client and Bindery see the same storage at different paths you need a path remap on the download client. And if the client is on Windows while Bindery runs in Docker, remaps were broken until this week, see #2191.

If you are still running it and it still is not importing, reply with what the queue says for one of them and I will look.