Page 1 of 1

Trouble Previewing Rule

PostPosted: Sun Apr 06, 2025 3:13 pm
by sccardais
When I try to preview a rule, I get this error dialogue.

Cannot change folder.
You can only preview files within the currently monitored folder.


The Finder window opens briefly but then loops back to the same message. As best as I can tell, I am actually in the folder associated with the rule.

Clicking OK sends Hazel into a loop. Ultimately, I have to force quit hazel.

I realize that macOS 15.5 is beta and this may be the root cause of the problem. In that case, I'm just adding the issue for the developer to investigate.

Re: Trouble Previewing Rule

PostPosted: Mon Apr 07, 2025 9:34 am
by Mr_Noodle
What version of Hazel are you running?

Re: Trouble Previewing Rule

PostPosted: Mon Apr 07, 2025 3:14 pm
by sccardais
I'm running Hazel v 6.0.4.

And, I'm running macOS v 15.5. I realize this is a beta version of the OS and that this might be the cause.

Thanks.

Re: Trouble Previewing Rule

PostPosted: Tue Apr 08, 2025 10:04 am
by Mr_Noodle
Does this happen on every folder or just particular ones? Can you send a video of this?

Re: Trouble Previewing Rule

PostPosted: Mon Jun 23, 2025 10:49 am
by adamlogan
I keep getting this too.

Here's a screen recording.

I have given Full File System permissions for Hazel.

The looping was too fast for me to read what directory was coming up. Looking through the frames of the screen recording I can see that it appears that my user's home directory is coming up rather than the monitored folder. So, that might be what's throwing the exception. Here's a screenshot of the freeze frame.

Excerpt of my Hazel log as well just for the time range when I did the screen recording.

All links in this post expire August 1, 2025 at 00:00 hours.

System / Version Info

Hazel Version 6.0.4

MacBook Pro
14-inch, 2021
Chip Apple M1 Pro
Memory 32 GB
Serial number LPW5Y7FFPR
macOS 15.5 (24F74)

Re: Trouble Previewing Rule

PostPosted: Tue Jun 24, 2025 9:24 am
by Mr_Noodle
Thanks for the video. Do you recall if this was an issue before 15.5?