Bug export and clone for rule machine legacy is broken

any clone operation on a rule machine legacy rule generates an error as shown below and generates a broken useless rule with nothing..

in addition export works and generates a text file but when trying to import it the import button is a no op-- ie it does nothing.

@bobbyD

1 Like

This isn't a Rule Machine thing; it's a general thing with the Import/Export/Clone utility. Victor is aware.

For now, re-creating the app is always an option (many of us remember when this was the only way :smiley: ), or you can consider temporarily downgrading to a platform version from before the problem started (probably 2.4.4.146, though I don't see a mention of what platform version you're running, which is always helpful for reports).

1 Like

you cannot recreate the app. if you try to add a new rule machine legacy rule (that is the point) it defaults to using the newer rule machine

Ah, yes, legacy...

In that case, you'd need the second option -- although, tangential to the point, I'd say using Rule 5.1 is now probably better unless you have a very specific need like direct access to a "legacy" global variable.

6 Likes

FYI, I’m hitting the error in 145, cloning a room lighting.

Yes, you'll see it with any app. It is being looked into:

4 Likes

Noted, fix on the way.

6 Likes

And where is the fix?

It's currently in beta.

4 Likes

Now available in production release .151

6 Likes