Hazel doesn't trigger automatically

Hazel has been consistently triggering on my Dropbox files again. Wonderful!

I'm not convinced that this is a Dropbox issue. I am having exactly the same problem, but my watched folders are not in Dropbox (although I do have Dropbox installed). Renaming the folder does not fix it. But removing and re-adding rules to the folder in Hazel does seem to fix it (at least for a while).

Seems like Hazel is being de-registered for fsevents on that folder, and the act of changing the ruleset will cause Hazel to re-register itself for fsevents on that folder?

Also seems like Hazel does also run rules on a timer, as a fallback. Perhaps Hazel should always re-register itself for fsevents on watched folders when it runs on a timer, as a work-around, if we cannot determine exactly why it is becoming de-registered to begin with.

See: viewtopic.php?f=4&t=2372&p=12286#p12286

If you are still having problems with this, email me at support as I may have a test build with extra diagnostics that may help isolate the problem.

I have the same problem.

Updates (new file added by IFTTT rule) to a Shared Dropbox folder does not trigger Hazel.

The rule actually moves the files to another folder in dropbox which equally doesn't fire when the first rule is force run. Its as if the files originating from dropbox don;t trigger rules - maybe it's the date created timestamp or something similar.

I'd be happy to try a debug version and provide rules and logs if that will help.

Worked reliably a month or so ago but has been dodgy for some time now.

Dropbox 2.6.5 on Mavericks 10.9.2 and Hazel 3.2.5

Well, I'm going to be releasing a new version this week. Unless you email me and are very quick to test it and report back, I'd wait until then.