Description of issue:
I am in the process of configuring Sonarr on my new Synology NAS however I am running into some strange issues. I read on the completed download handling wiki that Sonarr will only move instead of copy torrent files, if they are no longer being seeded and if the remove option is enabled.
Strange thing is, I do not have the remove option enabled and Sonarr is moving the files despite them still being seeded. Plus for some reason if the downloaded show comes in an archive (which Syno DS will automatically extract), it will only move the .mkv/.avi files. However if the show comes in a flat folder structure, after the move it will delete the entire folder. If I do a manual import and select the copy option, everything works as intended though.
I run several scripts on my download folder so it is necessary for me that the files remain in that folder. Is there a force copy option I can enable somewhere or do I need to open a bug for this on github?
I just installed Radarr, configured it exactly the same as Sonarr and to my suprise it is working correctly. Automatic processing copies the file correctly instead of moving/deleting the original download.
After some additional googling, I think I figured out the root cause. It seems someone wanted to achieve the opposite of what I am trying to do. Not really sure why the request was implemented, seeing as it deviates from the standard behaviour causing the default action to become move instead of copy for torrents in Download Station.
This is kind of annoying because the behaviour in Radarr is actually correct imho. I get the reasoning that it isn’t necessary to leave the original file as download station automatically makes an internal hardlink. However I run several scripts on my download folder so it is useful for me that the files remain there until I stop seeding or delete them. Plus as mentioned in my first post, if Sonarr moves an unrarred show, it does not delete the remaining rar files & folder.
Suggestions or workarounds on how to solve this are still welcome. Would it be useful to launch below feature request? I think the necessary code and API calls already exist and it could save us all some headaches.
