# Client-side break point or allert freeze node-red entirely

**URL:** <https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680>\
**Category:** Dashboard\
**Created:** [10 September 2020 08:07 UTC](https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680 "2020-09-10T08:07:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![0x180](https://avatars.discourse-cdn.com/v4/letter/0/8c91f0/32.png) [@0x180](https://discourse.nodered.org/u/0x180)\
**Post date:** [10 September 2020 08:07 UTC](https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680/1 "2020-09-10T08:07:05Z")

</div>

Greeting, as stated in the title i was digging into node-red (v.1.1.3) dashboard (v2.23.2).

May be it's just a mine missrepresentation of the problem, but when i open the dashboard (ctrl+shift+D) from a flow editor, I'am able to test the dashboard only if i don't put client-side break point o alert (to see what happened client side).  
If i do so (placing break point or alert) the entire node-red process freeze until client-side I move forward from break point or alert.  
How is that possibile? In my mind model, server side is a single process and single thread environment (as node server is), but server-side should deeply rely on async call, so that a client that hang or hit a break point would not lock it up the entire server.  
Am I miss something?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [10 September 2020 08:39 UTC](https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680/2 "2020-09-10T08:39:31Z")

</div>

This is in the browser only. Node-red its self is not affected. Only the editor and dashboard are.

This is easy to prove...

- Have a flow that increments a flow or global context value every second.
- Have you dashboard pause on a debug point or alert & leave it for 60 secs.
- close the alert / debugger
- check the value of the flow/global value being incremented

---

<div class="post-metadata">

**Author:** ![0x180](https://avatars.discourse-cdn.com/v4/letter/0/8c91f0/32.png) [@0x180](https://discourse.nodered.org/u/0x180)\
**Post date:** [10 September 2020 08:41 UTC](https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680/3 "2020-09-10T08:41:30Z")

</div>

Thank you to have clarify to me what i have miss interpreted.  
Now what i see make more sense

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [24 September 2020 08:41 UTC](https://discourse.nodered.org/t/client-side-break-point-or-allert-freeze-node-red-entirely/32680/4 "2020-09-24T08:41:49Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.