Receive now error messages on rules that worked before

You can email in the log if you like though if you do so, make sure to point out the times of events like reboots and such.

Email is out with the requested data.

Hey there,

I just had the same issue. I updated to macOS 15.2 yesterday and everything was fine. When I just moved a new file into a monitored folder I got a plethora of error messages. It seemed like Hazel was checking all files in the ~/Downloads folder for example and some rules with type checking had the same error as Ruhrpottjung experienced.

I did restart Hazel; no change. Spotlight indexing was up to date. I used Hazels "Preview Rule" functionality with different rules on the same file and other files/folders. Interestingly the error was not consistent:
Example:
Rule A checks if the file is a movie file:
- For file 1.pdf it errored out.
- For file 2.csv it worked.
- For folder dir1 it worked.
- For folder dir2 it worked.
- Again checking file 1.pdf - still same error.

Rule B checks if the file is a pdf file:
- For file 1.pdf it worked.
- For file 2.csv it got an error.
- For folder dir1 it got an error.
- For folder dir2 it got an error.
- Repeated with all files/ folders - same errors.

While I checked System Settings --> Spotlight I noticed that there is an option to help Apple to improve search. I'm not sure if this was always there or if it is new. I deactivated it and rebooted the system.

Aforementioned Rules A and B ran through and moved the files as expected.

System language is German as well.

So you are saying everything works fine after unchecking that? I think it might be a coincidence but who knows. Keep an eye on it.

Hello,

the disabling like mentioned from "PatrickStar" the section to help Apple to improve search. No error message popup.
I wrote you another email with a new created logifle after disabling the function mentioned by PatrickStar.

Very strange but if it works, then it works.

Saw this thread and want to chime in that I have the same issue. macOS 15.3.1 and Hazel version 6.0.4.

Over 60 (!) errors from Hazel when I boot up my machine. Hazel is trying to match pdf rules on just about any file in my downloads folder. Most rules have

Code: Select all: Kind is PDF

as the first step. Still these rules cause an error on dmg, zip, jpg, and other files.
Rule status and Rule preview show there is no match. However, the rules at boot time keep on showing in large amounts.
Did a rebuild of the Spotlight index. That too didn't help."Help Apple improve search" in the Spotlight settings is switched off.

Is it showing no match on the "Kind if PDF" condition? If you click on the red X, what "Kind" does it show?

One example when I just rebooted my machine.

Hazel throws an error on file xyz.rar. The rule it's mentioning in the error has as the first condition:

Code: Select all: Kind is PDF

When I preview the rule for file xyz.rar it shows

Code: Select all: Kind: Archive

For this particular case t

The same happens with zip files. And with pdf files that have multiple conditions, one of them being the filename ("Starts with xxxx"). The pdf file it throws an error for has a completely different filename.

All these show the following error:

Code: Select all: Could not retrieve metadata for file ...

That error indicates that Spotlight has not indexed that file. You'll need to do further diagnosis of what's going on with Spotlight on your machine.

Mr_Noodle wrote:So you are saying everything works fine after unchecking that? I think it might be a coincidence but who knows. Keep an eye on it.

When I disabled the system setting like mentioned from "PatrickStar" the section to help Apple to improve search it also seems to have fixed my issues as well as I mentioned in the "Hazel No Longer works with the downloads folder" thread. Errors in the log file have gone away, Hazel does not hang processing folders and previous rules that would not match anymore are now matching again? I have also noticed my system resources have dropped about 10%. I am still monitoring the situation but after a day in a half all seems to be working again? This issue appeared after upgrading from Sonoma to Sequoia 15.3.1