qBittorrent contributing to potential data loss when always resuming torrent after recheck when payload is not found

[slrslr]

Suggestion

From time to time, You find some errored torrents because you have renamed or relocated files using your OS file manager and forgot that these files are part of some torrent.

So in qBtittorrent (I am using latest 5.0.0 AppImage Libtorrent 2) You go to the errored torrents section. Change location of the torrent payload, but you accidentally set incorrect path or the payload file is still named differently. Then you click to recheck. The file disappear from the errored section so you loose track of it and must be lucky to remember its correct name to filter it out of the long torrents list.

Second problem, for which I have created this issue is that in case the torrent payload is not found during recheck, user have to be quick enough to find the torrent and stop it before it start downloading (because qbt sets it to a downloading state), so it often (in my case IMO always) qbt starts writing the data you usually already have in a different location. Maybe qbt can set that torrent as stopped or back as errored so user have it handy for next attempt?

Instead user finds resumed or downloading torrent and makes a second attempt to set the correct path or tries to rename the payload file name/s. During this qbt relocates incomplete payload and overwrites complete files downloaded earlier! https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aopen+is%3Aissue+label%3A%22Data+loss%22

Conclusion:
I see it as a smaller problem to set torrent as stopped (or back as errored) than 1) enabling data loss, 2) wasting data transfer by resuming download from zero and also 3) causing duplicity on disk.

Use case

No response

Extra info/examples/attachments

No response

[HanabishiRecca]

Set Settings > Downloads > Torrent stop condition to Files checked.

[slrslr]

I already have it set that way. For some reason, yours described option does not work for me for this particular case. I remember though that it worked for newly added torrents.