Despite having enabled SpotLight on the Networked Folder on the NAS according to the steps above.
https://prnt.sc/cmep9JmzJPCqShows that Spotlight is indexing on the Networked folder
Hazel is still showing the Spotlight issues, when the Hazel working folder is on the NAS.
https://prnt.sc/DeRNJZF9IuK3The more files I move into the Hazel working folder, the more "Could not Retrieve Meta Data" errors I get.
Looking at the notifications generated by Hazel, still it appears to work.
The options I have are
1) Use a local working folder in the internal Mac disk instead of the Networked Folder - still moving files to the NAS as destination.
2) Continue using the working folder on the NAS.
What do you suggest?
Moreover when I click on the rule status (Check the status of the current rules) and then on the rule information for one file,
that usually leads to this
https://prnt.sc/VQICUYN-Aqtf I obtained another uncaught exception:
Process: Hazel [5241]
Path: /Applications/Hazel.app/Contents/MacOS/Hazel
Identifier: com.noodlesoft.Hazel
Version: 5.1.2 (2274)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Hazel [5241]
User ID: 503
Date/Time: 2022-07-10 08:39:27.811 +0200
OS Version: Mac OS X 10.15.7 (19H1922)
Report Version: 12
Anonymous UUID: DE707EAF-7903-A06C-9733-4F92E57497C7
Time Awake Since Boot: 9500 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSException count]: unrecognized selector sent to instance 0x600002dd3180'
terminating with uncaught exception of type NSException
abort() called
It appears to be an uncaught exception, that happens when the file has been already been moved to its destination.
I decided to move the Hazel working folder to a local Mac folder, because obviously Hazel has too many issues here.
I will still keep the NAS as destination.