Hazel rules crash on embedded script

I have a number of rules designed to sort incoming monthly pdf statements into folders/subfolders contained within my Dropbox folder. These statements include bank, utility, credit card, and investments. All the rules use awk to extract the date from the pdf. I've had a good number of the rules crash after the first use, and the fix is to rebuild the rule identically including copying and pasting the scripts at which point things work fine. The rules match in the preview window but crash on the subsequent script. Duplicating the rule does not work; the duplicated rule also crashes. But a newly built rule, identical in every respect, works perfectly. This is not an issue where the date is moving around in the pdf and the script needs to be adjusted. It is simply that the rule, or a duplicated rule crashes every time where an identical rule built from scratch works fine.

Is it possible that something about dropbox is causing rules to crash? Should I change these scripts to move the statements initially to a folder not in dropbox and subsequently, with another rule that doesn't involve a script but only looks at the file name, move them to the appropriate dropbox folder?

Richard

Are these new rules? I anticipate the embedded script handling may have contained errors which have been fixed in a more recent version.

These are rules that worked on statements appearing in April and before. The May statements are now coming in and the rules no longer work although preview shows that the individual pdfs are recognized correctly. The failure appears to be in a script at the start of the "do the following..." section of the rule. If I duplicate the failing rule the duplicated rule fails as well. If I build a new rule, identical in every detail to the original, the new rule works.

I wondered if this might be due to sorting into Dropbox folders. But your question makes me wonder if there us some underlying failure in the old rule for which the only fix is to do as I have been doing and rebuild each rule from scratch. At this point every incoming statement that involves one of these substantially similar rules has failed and required that I build a new, identical rule. As a new user I guess what I am wondering is if this is going to be an ongoing problem which is why I was focusing on possible dropbox issues, or if it is more of a one time deal because of the 4/18 update to Hazel.

Thanks!

I've never used Hazel directly on Dropbox folders, and haven't seen your rules/scripts, but maybe the issue could be worked around by adding certain "Date …" conditions that delay Hazel actions to eliminate or reduce risk of interference with synching (if that's what's causing trouble now).

All of my rules with scripts operate within dropbox folders. I do to believe this is your issue. I might suggest posting the script.

I suggest emailing support with a copy of the rule that fails and the one that workse.