I'm not sure exactly when it happened (I have done the past few updates and not scoured the logs, etc.). However, I happened to see an unexpected error in one of my RM 5.1 rules and got to looking into it--and now I see SEVERAL rules have numerous "Broken Action" lines. [image] [image] [image] L…

[image] 672southmain: Is there anything special we have to do after we install this platform update? It should just fix the problem. Nothing special to do. Let me know...

Hmm. So, I rolled back to .132 and my rules looked intact again (at least when I examined them all after the rollback). Do I need to be going back before that (i.e., to .129)? And, do I need to restore the entire DB? Or, should I be safe with just the platform rollback to .132? And not touching any…

[image] bravenel: It was introduced in Release 2.3.1.130. That was March 26 or 27 I think. Then may I respectfully suggest that, until a fixed platform version is released, one of the staff magicians make the “Download latest version” button in Diag Tools cause 2.3.1.129 (version before the i…

With all due respect, it's Friday night. I can't promise that anything can be done before Monday, and the most likely thing to happen is a hot fix. Something might happen prior, but that's not known at this time.

It's 11:42 PM EDT! Just being realistic.

I thought all you guys lived in a house together in Arizona. :slightly_smiling_face:

Was on 132, noticed no "Broken Actions" but found errors running a rule setting a local variable to a device attribute (sensor value). Rolled back to 129 (with current database), now the rule showed "Broken Action", threw an error and needed to be manually fixed. YMMV 132 Error [image]

[image] arnb: Rolled back to 129 (with current database), now the rule showed "Broken Action", threw an error and needed to be manually fixed. YMMV Yeah, there is an incompatibility between 129 and later builds with respect to setting a variable to a device attribute. Best plan is to sit tig…

[image] bravenel: which will be today As usual, HE staff goes above and beyond on dealing with issues that arise. Companies I've worked at/with in the past would not even be aware/looking at this until mid-day on Monday at best, maybe a fix by the end of the week. Just another reason why HE i…

Hot fix that fixes this problem coming shortly. 2.3.1.134.

[2.3.1.133 C7] Massive numbers of "Broken Actions"

Rule Machine® All things Rule Machine

danabw April 2, 2022, 4:30pm 24

Wow...and .134 is already out!