
I see. Looks like it was a permissions issue after all.

FileBot correctly identified the file at hand, tried to name / organize it accordingly, but failed to to a permissions issue:
Console Output: Select all
Rename movies using [TheMovieDB]
Auto-detect movie from context [/volume1/data/torrents/completed/Blazing Fists 2026 1080p (DUAL) WEB-DL HEVC x265 5.1 BONE.mkv]
[MOVE] from [/volume1/data/torrents/completed/Blazing Fists 2026 1080p (DUAL) WEB-DL HEVC x265 5.1 BONE.mkv] to [/volume1/PLEX/Movies/Blazing Fists (2025) {tmdb-1363103}/Blazing Fists (2025).mkv]
[MOVE] from [/volume1/data/torrents/completed/Blazing Fists 2026 1080p (DUAL) WEB-DL HEVC x265 5.1 BONE.mkv] to [/volume1/PLEX/Movies/Blazing Fists (2025) {tmdb-1363103}/Blazing Fists (2025).mkv] failed due to I/O error [Access Denied: /volume1/data/torrents/completed/Blazing Fists 2026 1080p (DUAL) WEB-DL HEVC x265 5.1 BONE.mkv -> /volume1/PLEX/Movies/Blazing Fists (2025) {tmdb-1363103}/Blazing Fists (2025).mkv (rw-r--r-- 1028:65536 Blazing Fists 2026 1080p (DUAL) WEB-DL HEVC x265 5.1 BONE.mkv -> rwxrwxrwx 106247:106247 Blazing Fists (2025) {tmdb-1363103})]
Processed 0 files
Error: Select all
... failed due to I/O error [Access Denied: ...]

Since you have enabled
Unsorted, FileBot did try to move the files elsewhere in a second step which also failed with the same
Access Denied error message.

I strongly recommend reading the console output when something does not work, or at least copy & pasting it into ChatGPT to summarize. Permissions can be tricky, that's why we say
"it's always permissions" here in the forums.

If you set permissions on the share then those should apply to the entire share by default. I could imagine that if you already have overriding permissions in subfolders, then something could go awry that way. But I don't know. You'd have to look at the permissions before / after you made it work and see. That said, if setting read/write permission on the share doesn't work, then I recommend reporting the problem to Synology technical support. A top-level setting like this definitely does not / should not apply to to just that one share folder but of course the entire share.

Lastly, on an unrelated note, I recommend
using hardlinks so that you can have the file twice at the original file path for seeding, and in the Plex file path for viewing, without using any additional disk space. That bit is up to you though, but if this is the first time you read about
hardlinks, then you definitely want to look into that.