Cross‑seed issue: torrent matched on tracker C but not tracker B (same file, same structure)

[doodz]

Hello,
I’m encountering an issue with the cross‑seed feature in qui.
I have 3 trackers (A, B, C).
When I add a torrent coming from tracker A, qui successfully finds and matches the equivalent torrent on tracker C, but not on tracker B, even though:

it is exactly the same torrent,
same release name,
same directory structure,
same content.

I use Prowlarr as my Torznab source, and I have also integrated Sonarr and Radarr into qui to improve ID‑based matching (as recommended in the documentation).
[crossceed.com]
From the Prowlarr logs, I can confirm that tracker B does return the expected torrent when queried.
This suggests that qui receives a valid candidate but rejects it internally for some reason, or never considers it a valid match.
Unfortunately, I have no visibility into why the match is rejected.
Would it be possible to have more detailed logs, or a way to display:

why a candidate was rejected,
whether it failed fuzzy/partial matching,
whether the file tree comparison failed,
whether reflink/hardlink layout creation failed,
or if the tracker’s Torznab response was filtered out earlier?

This would greatly help diagnosing the issue (possibly a misconfiguration on my side, or a tracker‑specific edge case).
Thanks in advance, and thank you for the amazing work on qui.
Doods

[Caedendi]

I am having this same issue with multiple torrents. I get that the cross-seed functionality may not be as robust yet as existing tools for uploads that don't 100% match but it is very strange when releases with exactly the same name/files/size don't get matched.