Hazel & Mavericks: Ghosts Rules

Hi everyone,
I've got something strange going on. It seems as though
a) Hazel is caching some of my rules
b) There is a phantom Hazel process that is running and I can't stop, even with a reboot.
Here's what's happening:
1) I've got a rule that processes photos, renames & moves them. Previously, it was appending the Lat & Long to the file name.
2) I removed the lat / long part & changed it to a timestamp.
3) I then dropped 33 photos into my directory to test. The new & old rules were bring run, resulting in over 33 photos being moved to the destination directory. It's not exactly 2-to-1, but I think that's because the new rule moves the file before the old rule can see it. So I'm left with a directory w/ a mismash of files, some named the new way, some the old. some are the full file and some are 0kb.
Here's where it gets weird:
4) I've disabled the rule, same result.
5) I've paused the rules from being run in that directory, same result.
6) I've stopped Hazel altogether, same result.
7) I've rebooted, same result.
Anyone seen something like this?
I've got something strange going on. It seems as though
a) Hazel is caching some of my rules
b) There is a phantom Hazel process that is running and I can't stop, even with a reboot.
Here's what's happening:
1) I've got a rule that processes photos, renames & moves them. Previously, it was appending the Lat & Long to the file name.
2) I removed the lat / long part & changed it to a timestamp.
3) I then dropped 33 photos into my directory to test. The new & old rules were bring run, resulting in over 33 photos being moved to the destination directory. It's not exactly 2-to-1, but I think that's because the new rule moves the file before the old rule can see it. So I'm left with a directory w/ a mismash of files, some named the new way, some the old. some are the full file and some are 0kb.
Here's where it gets weird:
4) I've disabled the rule, same result.
5) I've paused the rules from being run in that directory, same result.
6) I've stopped Hazel altogether, same result.
7) I've rebooted, same result.
Anyone seen something like this?