Hazel tries to run rules on folder that was removed

I have a rule set up in Hazel that simply monitors a folder for new files and moves them to another folder. I changed restructured my folders so the old destination no longer exists. I then went into Hazel, saw that the old destination was dimmed (indicating the folder couldn't be found) and I changed the rule to point to the new destination. The rule works fine, but I'm getting tons of log messages: "/Data/Pictures/Lightroom Originals/Auto-Import Temp Location: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

I've noticed that the old destination, while not in use by any rule, is still in the dropdown list that appears when selecting a destination folder.

How can I stop these console messages? They are so frequent, it's hard to read the log files.

Thanks.

Try logging out and back in and see if that clears things up.

Thanks for the quick reply. Unfortunately, that didn't fix it. The changes I described in my original post were done several months ago. So, there have been multiple reboots of my machine since. I tried it anyway just in case.

Any other suggestions?

Can you post a larger excerpt from the logs. It seems some rule is still referencing that folder somewhere.

You just gave me the hint I needed. I checked all of my rules and found an old when I had forgotten that referenced the missing folder. :oops:

I corrected it and the errors went away.