Hazel not running rule automatically

You'll need to add conditions to take that into account. You haven't really explained the files in question or their inter-relationship but one quick way to fix things, if the files are supposed to appear almost at the same time, is to add a delay. Something like "Date added is not in the last X minutes".

The better solution is to use a couple of nested conditions to see if the other files exists. Again, I don't know how the files are related so I can't provide anything more specific than that.

I was able to solve the problem by adding "continue matching rules" when it matches the XML file. This forced Hazel to process the rules pertaining to the TIFF I'm trying to rename based off of information inside the XML. Thanks for your help on this Mr. Noodle!

Not to hijack your thread but I have been having a similar issue. It's actually been happening for a year but I just lived with it until now.

Using latest version. On Yosemite 10.10.5

Mr Noodle, do you think you could supply me with that debug version? I have a secondary internal SATA housing all my content. Once files are added to a particular folder, hazel often will not process them until I run the rule manually. It seems to "break" on the same two folders (each with different rules). A temp fix is to force quit hazel and Reload. This gets it to auto process for a bit but then it stops and requires a manual load. I've tried the usual readd folders, rules etc. files match the right rule just doesn't run. Log sometimes shows rule has not run even though it should have; other times it will show a match but rule has not run. Drives me crazy.

I'm continuing to have this problem too. I've added a "Run Rules on Folder Contents" at the end of a lot of my rules, and that seems to help... sometimes. My problem did not occur until upgrading to Hazel 4.

This is a poor "solution" to the problem -- which is probably user error on our parts in some way....but

I created a shell script that wraps up apple scripts (run via osascript command) to run certain hazel rules manually via GUI scripting. I schedule it with Lingon (an interface for launchd -- although you can just schedule it via launchd directly if you know how) to run every 30 minutes. Again, i am doing this to run these outside of Hazel's core event handler capabilities until i figure out what is causing the issue with Hazel.

See the link below to the shell script. All you should have to do is change the name of the hazel rule (listed one time) in each osascript command (NOTE: mine are named NZB_tv, NZB_movies, etc). Delete or add osascript commands as needed.

Note: When you run for the first time, you will have to give the script permission to control your computer via Security & Privacy / Accessibility in System Prefs. Just add it to the list by clicking on the check box once you are asked to give permission by the system.

https://ufile.io/5ee1

BTW, please email in to support with the results from this article: https://www.noodlesoft.com/kb/hazel-tro ... ing-guide/

The causes vary quite a bit so it's not one particular problem here.