# Node red crash with bad node parameter

**URL:** <https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671>\
**Category:** General\
**Created:** [6 February 2019 19:17 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671 "2019-02-06T19:17:23Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuriy](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yuriy](https://discourse.nodered.org/u/Yuriy)\
**Post date:** [6 February 2019 19:17 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/1 "2019-02-06T19:17:23Z")

</div>

I'm new to Node-Red. It's happened to get Node-Red crash by changing one of node parameters (Modbus TCP - ip address); moreover Node-Red failed to re-start due an uncaught exception during loading of flows.  
Eventually, i changed manually of json flows file by using back door and all started back.

And here question: Are there should be a better handle in back-end for managing such scenarios?  
I'm come from industrial automation and from my point of view one bad flow should not interference with other and whole server.  
Or i did some wrong, or here more things to config?  
any feedback appreciated, thanks.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [6 February 2019 19:19 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/2 "2019-02-06T19:19:47Z")

</div>

That’s a problem with that node and ideally you would open an issue with the author to get it fixed. You should be able to find a link to the nodes github page from the nodes page on [flows.nodered.org](http://flows.nodered.org)

---

<div class="post-metadata">

**Author:** ![Yuriy](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yuriy](https://discourse.nodered.org/u/Yuriy)\
**Post date:** [6 February 2019 19:29 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/3 "2019-02-06T19:29:05Z")

</div>

I like whole concept, but a lot of questions arises about internal architecture, thanks anyway.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 February 2019 20:07 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/4 "2019-02-06T20:07:05Z")

</div>

Hi @Yuriy

If an asynchronous error is left uncaught we catch it in a global exception handler. At this point we do not know which node or module was responsible for the error. We don't know what has caused the error and we have no way of isolating or restarting just that part of the flows.

Here's what Node says about uncaught exceptions: [Process | Node.js v21.5.0 Documentation](https://nodejs.org/api/process.html#process_warning_using_uncaughtexception_correctly)

> Attempting to resume normally after an uncaught exception can be similar to pulling out of the power cord when upgrading a computer — nine out of ten times nothing happens - but the 10th time, the system becomes corrupted.  
> The correct use of `'uncaughtException'` is to perform synchronous cleanup of allocated resources (e.g. file descriptors, handles, etc) before shutting down the process. **It is not safe to resume normal operation after `'uncaughtException'` .**

Emphasis all theirs.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [6 February 2019 20:54 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/5 "2019-02-06T20:54:32Z")

</div>

Their is one improvement which I believe is coming along shortly, which will allow node-RED to be started in Safe mode where it runs the editor but does not start the flows. This will allow more easy recovery from such problems.

---

<div class="post-metadata">

**Author:** ![Yuriy](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yuriy](https://discourse.nodered.org/u/Yuriy)\
**Post date:** [6 February 2019 21:30 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/6 "2019-02-06T21:30:37Z")

</div>

Isolation UI & script execution && each flows will be huge step ahead.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 February 2019 21:42 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/7 "2019-02-06T21:42:56Z")

</div>

you could also run multiple instances on one machine if you like, each with their own "isolated" flow.

---

<div class="post-metadata">

**Author:** ![Yuriy](https://avatars.discourse-cdn.com/v4/letter/y/ea666f/32.png) [@Yuriy](https://discourse.nodered.org/u/Yuriy)\
**Post date:** [6 February 2019 21:52 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/8 "2019-02-06T21:52:41Z")

</div>

😄 Thanks.

But i' think it is not solution for production in my case.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [3 July 2019 13:52 UTC](https://discourse.nodered.org/t/node-red-crash-with-bad-node-parameter/7671/10 "2019-07-03T13:52:36Z")

</div>

> [@Colin](#):
>
> Their is one improvement which I believe is coming along shortly, which will allow node-RED to be started in Safe mode where it runs the editor but does not start the flows.

This thread predated the creation of safe mode, why are you resurrecting old threads?