Noodlesoft Forums

Both ‘Rule → Preview Rule…’ and ‘Rule → Rule Status…’ indicate a match for my Rule ‘Move JMG Invoices’, but the Rule’s Action is NOT being performed:

Code: Select all

2022-10-06 08:05:37.105 hazelworker[74786] Running worker (v5.1.4) for folder with identifier: 16777220-874919.
2022-10-06 08:05:37.137 hazelworker[74786] ###Arch: x86_64
2022-10-06 08:05:37.137 hazelworker[74786] ###main load address: 0x104546000
2022-10-06 08:05:37.138 hazelworker[74786] ###Hazel Core load address: 0x104821000
2022-10-06 08:05:37.138 hazelworker[74786] ###Noodle load address: 0x104b42000
2022-10-06 08:05:37.138 hazelworker[74786] ###CK load address: 0x104701000
2022-10-06 08:05:37.244 hazelworker[74786] Processing folder Downloads (forced)
2022-10-06 08:05:40.220 hazelworker[74786] Investment Advisory Invoice 56510 Dated 10-03-2022.pdf: Rule Move JMG Invoices matched.
2022-10-06 08:05:40.221 hazelworker[74786] Caught exception in rule evaluation of file Investment Advisory Invoice 56510 Dated 10-03-2022.pdf: [<HazelFileData 0x600002d4cc60> valueForUndefinedKey:]: this class is not key value coding-compliant for the key hazelcustomtoken:invoiceNumber.
2022-10-06 08:05:40.221 hazelworker[74786] ###Arch: x86_64
2022-10-06 08:05:40.221 hazelworker[74786] ###main load address: 0x104546000
2022-10-06 08:05:40.221 hazelworker[74786] ###Hazel Core load address: 0x104821000
2022-10-06 08:05:40.221 hazelworker[74786] ###Noodle load address: 0x104b42000
2022-10-06 08:05:40.221 hazelworker[74786] ###CK load address: 0x104701000
2022-10-06 08:05:40.222 hazelworker[74786] (
   0   CoreFoundation                      0x00007ff81ce38773 __exceptionPreprocess + 242
   1   libobjc.A.dylib                     0x00007ff81cb98bc3 objc_exception_throw + 48
   2   CoreFoundation                      0x00007ff81ce61056 -[NSException raise] + 9
   3   Foundation                          0x00007ff81dd50448 -[NSObject(NSKeyValueCoding) valueForUndefinedKey:] + 225
   4   HazelCore                           0x0000000104832c66 hasNSRecords + 16602
   5   Foundation                          0x00007ff81dbe9fc0 -[NSObject(NSKeyValueCoding) valueForKey:] + 307
   6   HazelCore                           0x000000010488c815 _isDateValue + 54918
   7   HazelCore                           0x000000010488c8a0 _isDateValue + 55057
   8   HazelCore                           0x00000001048934dc _isDateValue + 82765
   9   HazelCore                           0x0000000104892eec _isDateValue + 81245
   10  HazelCore                           0x0000000104889c26 _isDateValue + 43671
   11  HazelCore                           0x0000000104893082 _isDateValue + 81651
   12  HazelCore                           0x0000000104889a15 _isDateValue + 43142
   13  HazelCore                           0x000000010486e987 errorFromOSAScriptErrorDict + 191522
   14  HazelCore                           0x0000000104856133 errorFromOSAScriptErrorDict + 91086
   15  hazelworker                         0x000000010454cda8 hazelworker + 28072
   16  hazelworker                         0x000000010454f7e4 hazelworker + 38884
   17  hazelworker                         0x0000000104551b3d hazelworker + 47933
   18  dyld                                0x0000000110ca752e start + 462
)
2022-10-06 08:05:41.324 hazelworker[74786] Done processing folder Downloads


Does this indicate a bug in Hazel?

Code: Select all

2022-10-06 08:05:40.221 hazelworker[74786] Caught exception in rule evaluation of file Investment Advisory Invoice 56510 Dated 10-03-2022.pdf: [<HazelFileData 0x600002d4cc60> valueForUndefinedKey:]: this class is not key value coding-compliant for the key hazelcustomtoken:invoiceNumber.


Yes, dejavu with my post earlier this year.

Check your rules. It looks like there is a corrupted custom attribute in there somewhere that you need to remove/replace.

Mr_Noodle wrote:It looks like there is a corrupted custom attribute in there somewhere that you need to remove/replace.

The offending Action had renamed my match token with a preface something like “hazeltoken…”

I removed this bogus token, replaced it with the correct token, and saved the Rule. Unfortunately, the Action was still not performed. When I opened the Rule again I found that the replaced token was again renamed to the same bogus name.

I created a new Action from scratch, deleted the old Action, and saved the Rule. It worked correctly.

Thank you for telling me what to look for. (I don’t understand what exactly the corruption was or how it happened, but I guess that it doesn’t matter.)

You wouldn't happen to have an old copy of the rule? If so, if you could export it and send it in, that would be appreciated. If not, then keep an eye out and if find you can replicate it again, let me know.

Mr_Noodle wrote:You wouldn't happen to have an old copy of the rule?

No, sorry, I deleted it.

Is there a (simple) way that I could recover it from a Time Machine backup?

You can but it's a bit of a hassle. Don't worry about it but if it does happen again, email in to support. Thanks.

Mr_Noodle wrote:You can but it's a bit of a hassle.

Yes, that’s what I figured.

I’ll try to keep this in mind.

Thank you.