Hazel Seems to Ignore New Files

I have Hazel configured to monitor my downloads folder (/Users/jmartin/downloads). I have a rule configured to match PDF statements downloaded from my loan processor and then move those PDFs to a different folder with a different name. Everything works fine if I manually run the file but Hazel doesn't seem to notice the new, downloaded, file on its own or to run the rules automatically at all.

I'm running Hazel 3.0.11. This worked perfectly back on Hazel 2 but I don't think it's worked right since I upgraded to Hazel 3.

I downloaded a matching file at 0621 and, after reimporting my rules, Hazel did run and move it at 0644. I downloaded another matching file at 0658. So far, I've waited 19 minutes and Hazel hasn't noticed the new file or processed it in any way.

Rule logic:
If any of the following conditions are met for the file or folder being matched:
Name is dxweb
Name is dwsup

Do the following:
Rename with pattern: ...
Move to folder: ...

Here's my debug log, covering the initial matching. I notice that the calculated next scheduled run for the folder is "5828963-12-19 18:00:00.000". That looks like a date with a year impossibly far in the future. Is that something to worry about?

debug log: https://www.dropbox.com/s/0bp788smoabveqf/hazel_log.txt

Could you send me the logs at the times when the files were added (06:21 and 06:58)?

I can do that when I get home, but the logs don't really show anything. Even in debug mode, Hazel goes quiet for long periods of time and doesn't log anything. I looked at the full log before I created this topic and I'm pretty sure that there were no log entries at either 06:21 or 06:58.

Try logging out and back in and see if that resets anything. Also, is the download folder on your boot drive or is it somewhere else?

It's on my boot drive.

I don't think that a logout / login cycle will change anything. I upgraded to Hazel 3 months ago and I've been through multiple reboots (and a Mountain Lion upgrade) since then. The rule hasn't worked since the Hazel 3 upgrade. I'm pretty sure about that because I remember being surprised that it wasn't moving given that I upgraded because Hazel 3 was supposed to be faster to notice changes and lighter on system resources.

I'm just now getting around to reporting an old problem.

I thought I was having a similar problem, but after further review ... It was a scripting issue which I finally have resolved.
I deleted my earlier post.

How about renaming the downloads folder to something else then renaming it back?

Huh. That seems to have worked. Thanks.

Ah good. It's an odd bug in the OS X kernel, unfortunately but at least it's working now.

Exact same issue here. I renamed the watched folder to something different and then Hazel threw all kinds of errors in the log then I renamed it back to its original name and everything works as expected now. Thanks for the solution.

Great.
It has worked for me too.

Thank you very much
Fabio