Then I have this folder being monitored by Hazel where I have this rule:
When I copy the file to that folder, I always get this message:
Thing is, there's no issue with the name being too long or anything, because if I rename the file to actually be
5 - Sir Giant - Still Here2 - SNB - 20241001_5h19m18sPM
which is what Hazel would do, I am able to copy the file to that folder without warning, so it seems that there's something going on when it comes to Hazel.
Short file, no Hazel running = copies the file
Long file, no Hazel running = copies the file
Short file, Hazel running = error message.
The monitored folder is a secondary drive I have inside my laptop. I just tested with a folder on my main drive and I am able to copy, rename, etc, so it seems to be a conflict with Hazel and the secondary drive. Why would that be the issue, when I am able to manually copy the file without any message, but when it comes to Hazel, it doesn't let me copy?
But there's more: the original rule was a bit more "complex": it would rename the file first, then it would move it to a folder called "Processed", in the same monitored folder. Then I would have that "Processed" folder as a monitored folder and that would copy the file to 2 different locations: Dropbox and iCloud Drive folders.
So:
Safety Net Backups (monitored) > Rename > Move to Processed folder
Processed folder (monitored) > Copy to Dropbox and iCloud Drive folders
For some weird reason, despite showing the error, it would somehow copy the file to Processed and the file was copied to Dropbox and iCloud, but inside Process it would be faded:
(you can see that only 1 file has zero bytes, but all the others have the full size. One is not faded.Inside Dropbox:
