I started NR today and saw this interesting message. Trying to follow the rabbit I got nowhere fast. See pictures. Ok, if the node got an erroneous message... But that "string" would need to come from somewhere. That text is not something I would be sending as a user string. It would be a f…

Thanks to both of you for the replies: @kuema and @bakman2 I think I found it. Else where on another machine I was/am injecting things and they were not really at the right point. Thus a message got to go to places it wasn't mean to be. I hope it is now fixed. Thanks both.

drmibell 16 August 2019 03:19 15

Fixed in version 0.2.4, uploaded to npm.

1 Like

[NEW FEATURE] node-red-contrib-queue-gate (version 1.2.0)

Topic		Replies	Views
Error detecting really not "working" General	8	765	27 September 2019
Help tracking this error - oops General	17	1023	24 January 2020
Debug node causing RangeError: Maximum call stack size exceeded General	29	3003	5 August 2020
Stuck with things happening in rare conditions General	8	103	29 September 2024
Node.error() not caught in Catch node General	2	6266	4 July 2018

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

I am not understanding this "error" message I get when NR starts

Related topics