No Log Errors, No Growl Errors, No Console Errors, & No Sort

Hazel simply does not sort for a particular folder that I have. I am wondering if anyone has seen this.

Here's a description:
Preview Rules Matches Every File I want it to
Only using "Sort into Subfolder" actions w/ growl alerts, all of which sort into existing subfolders

Here's what I did that had no effect:
Run Rules Now
No Hazel Log Errors
No General Console Errors
No Growl Alterts of Hazel Errors
All other folders work properly
Start-stop Hazel
Log out, log in
Restart
Delete Folder structure, let "Sort into Subfolder" do it

I've been using Hazel for years, but this is the first time I am speechless. Any ideas?

If this happens to anyone else - here is the solution:

For me, there was a custom "match" field that was present in an "action" but its corresponding "rule" did not create the field.

Confusing explanation...

Here's an example:
My rule used to be:

If Name Matches (CUSTOM MATCHING STRING) then

And my action was

Sort into Subfolder (CUSTOM MATCHING STRING)

Then, I changed the rule:

If Name Matches (ANYTHING) (DIGITS) then

But I accidentally left:

Sort into Subfolder (CUSTOM MATCHING STRING)

Clearly a bone-headed move on my part, but difficult to find if it's hidden at the end of a long growl notification (my case).

@Mr_Noodle - is there any reason why this wouldn't show up in the logs, or make a crash report? I find that odd...

Feature Suggestion: Idiot-Proof Custom Token Proper Use Debugger

Is (CUSTOM MATCHING STRING) a custom token? If so, when you remove it from the condition above, it should delete itself from any patterns in the actions below. If this is not the case, let me know (hopefully with a recipe to replicate it).

Yes, (CUSTOM MATCHING TOKEN) was a custom-named token, and no - it did not automatically delete when it was already part of an action.

This is the series that caused the error:

Create a rule with custom token matching; action containing a Growl alert with custom token matched
Duplicate rule
In duplicate rule, delete (or modify) the rule section, but do not change the growl alter.

With this series, the custom token stays when it shouldn't.

Well, I can't replicate your specific problem but I did find a bug deep down in this part of the code. There's a somewhat random element to it which may account for it breaking in a different way for you. I'll probably do a beta of this next release so I suggest confirming whether this fixes it for you when that is done.

Could you try this again in the beta (2.3.5b1) I just posted (details in the beta forum)? Again, I couldn't get it to behave like how you were seeing it but I did find a bug in that area so maybe it fixes that as well.

Post replies in the beta thread. Thanks.