Logon screen timeout

[Snowman]

@toggledbits These errors are on the UI. Not from the logs. They are not preventing me from doing any work.

For example, I'll go to Expressions, click the Add Expression, and when I click the Save Changes button, that is when these errors pop-up.

Same goes with creating or updating a rule.

I'll post a screenshot next time I see one.

I'll try the Clear local storage suggestion and will let you know.

[toggledbits]

@Snowman said in Reactor-Editor / Reactor-ui-Status Errors:

For example, I'll go to Expressions, click the Add Expression, and when I click the Save Changes button, that is when these errors pop-up.

All of the errors you showed are in the context of the Rule Editor being active. Can you show an error message from using just the Expressions tab as in your example?

@Snowman said in Reactor-Editor / Reactor-ui-Status Errors:

I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.

So, this is progressive? Does it ever happen on the first use of the tab/function? Is it not resolved temporarily by simply refreshing the page/UI?

[Snowman]

@toggledbits Below, the error and a screenshot while creating a new Global Expression, named "test". Hoping this helps answer your questions.

As soon as I am done typing "test" and clicking in the field to add my formula, the error pops-up and will continue popping-up three times by the time it saved the changes. The error will also pop-up when I delete the expression and will pop-up a second time by the time it saved the changes.

It did not happen on the first use of the tab/function. It took a few tries before I could re-produce the error. It does resolve itself after a page refresh.

@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91
makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68
each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35
@http://192.168.0.13:8111/client/MessageBus.js:98:44
forEach@[native code]
@http://192.168.0.13:8111/client/MessageBus.js:95:54
@http://192.168.0.13:8111/client/MessageBus.js:106:44
@http://192.168.0.13:8111/client/Observable.js:78:28
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21
signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29
reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32
@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40
dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040

[toggledbits]

That's... crazy. You know those things programmers say "should never happen"?

It's that.

Digging.

[therealdb]

I have similar popups, but I was never able to precisely replicate that. I'll keep an eye on the next and I'll report here as well.

[tunnus]

Just got a runtime error in UI (build 24343) when I deleted a newly created rule. Before deleting this rule, I copied reactions to it from another rule. It also contained local variables (if that matters).

TypeError: Cannot read properties of undefined (reading 'getID')
    at Data.getLongID (http://192.168.**.**:8111/client/Data.js:172:37)
    at Data.toString (http://192.168.**.**:8111/client/Data.js:164:55)
    at Data.getBusName (http://192.168.**.**:8111/client/Observable.js:65:32)
    at RuleEditor.subscribe (http://192.168.**.**2:8111/client/Observer.js:91:200)
    at RuleEditor.updateCurrentServiceValue (http://192.168.**.**:8111/reactor/fi-FI/lib/js/rule-editor.js:1094:34)

(macOS Sequoia & Chrome)

[toggledbits]

@tunnus said in Reactor-Editor / Reactor-ui-Status Errors:

Just got a runtime error in UI (build 24343) when I deleted a newly created rule. Before deleting this rule, I copied reactions to it from another rule. It also contained local variables (if that matters).

I need a detail of every single step taken up the error popping up. Click by click, key by key. Also need to know what conditions were in the rule, and what actions were in the reactions.

[vezinpi]

I do not think that this issue is limited to MAC computers. I also have seen similar errors with Chrome from a PC running Win 11.

[toggledbits]

@vezinpi said in Reactor-Editor / Reactor-ui-Status Errors:

I do not think that this issue is limited to MAC computers. I also have seen similar errors with Chrome from a PC running Win 11.

Do you have any more detail? I can't really do much with a "me too" post.

[vezinpi]

@toggledbits Sorry about that. I wrote a second post following that one but probably never hit submit. My bad

MSR Version 24302

I simply push the play button for the "Set reaction" of a rule. The action performed as expected even with the error message. (since this happened yesterday, I am just re-typing the error from the screen capture for easy reading)

EDIT 1: I noticed that the error message was showing 15 second after I push the play button. Since I have a delay in the "Set reaction", I try to remove it and this error is gone. Somehow the delay I am using prior to the "Entity Action" is causing this timeout error.

Error: Command timeout (195 start_reaction) at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/clientAPI.js:552:136)

Here is a different one, more inline with this post, that I just did by editing a "Date/Time" trigger from 8:05h to 8:10h and save. The error message occured when I pushed the save button. The action (save) actually work despite the error message.

TypeError: Cannot read properties of undefined (reading 'getEditor')
at RuleEditor.makeExprMenu (http://192.168.2.163:8111/reactor/en-US/lib/js/rule-editor.js:1788:86)
at Object.handler (http://192.168.2.163:8111/reactor/en-US/lib/js/rule-editor.js:2174:54)
at http://192.168.2.163:8111/client/MessageBus.js:49:44
at Array.forEach (<anonymous>)
at MessageBus._sendToBus (http://192.168.2.163:8111/client/MessageBus.js:46:54)
at MessageBus.send (http://192.168.2.163:8111/client/MessageBus.js:57:44)
at ExpressionEditor.publish (http://192.168.2.163:8111/client/Observable.js:51:37)
at ExpressionEditor.notifySaved (http://192.168.2.163:8111/reactor/en-US/lib/js/ee.js:82:14)
at ExpressionEditor.notifySaved (http://192.168.2.163:8111/reactor/en-US/lib/js/expression-editor.js:47:15)
at http://192.168.2.163:8111/reactor/en-US/lib/js/reactor-ui-rules.js:1459:28

[toggledbits]

@vezinpi said in Reactor-Editor / Reactor-ui-Status Errors:

EDIT 1: I noticed that the error message was showing 15 second after I push the play button. Since I have a delay in the "Set reaction", I try to remove it and this error is gone. Somehow the delay I am using prior to the "Entity Action" is causing this timeout error.

That issue was known and handled in 24343.

For the other message, can you show all the conditions and reactions in the rule?

[vezinpi]

Thanks for the update and sorry about the timeout issue, I was not aware of it.

Here is the requested rule: