# Feature Request? If a flow has unknown nodes, is disabled, do not stop all flows?

**URL:** <https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053>\
**Category:** General\
**Created:** [31 December 2025 04:43 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053 "2025-12-31T04:43:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jibun-no-Kage](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jibun-no-kage/32/99316_2.png) [@Jibun-no-Kage](https://discourse.nodered.org/u/Jibun-no-Kage)\
**Post date:** [31 December 2025 04:43 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053/1 "2025-12-31T04:43:25Z")

</div>

Feature Request? If a flow has unknown nodes, is disabled, do not stop all flows?

I am in the process of updating some very old flows, which of course used old native dashboard. So I get the applicable 'unknown' nodes warnings. But these are warnings, not errors (yellow not red). So why are all flows stopped? Moreover, if I disable the flow, why are all flows stopped? I understand unknown nodes can be an issue but I fail to understand why all flows are stopped, even more boggles my mind, if the given flow is disabled, why all flows disabled?

Would it not make sense to only disable the flows that have unknown nodes? Or require the operator to disable the problem flow, but let other flows function? What is the risk if the flow is explicitly disabled?

As I am migrating the flows, I am optimizing and improving them, so I am creating a new flow, by referring to the old flow only by reference, as I recreate the new version, but since all flows for the entire NR instance or disabled, it makes it very difficult to reference the old flow while creating the new flow.

---

<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:** [31 December 2025 08:04 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053/2 "2025-12-31T08:04:32Z")

</div>

You can install the original dashboard alongside the new one, they will not affect each other.

---

<div class="post-metadata">

**Author:** ![Jibun-no-Kage](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jibun-no-kage/32/99316_2.png) [@Jibun-no-Kage](https://discourse.nodered.org/u/Jibun-no-Kage)\
**Post date:** [7 January 2026 03:20 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053/3 "2026-01-07T03:20:03Z")

</div>

Yes, realized that... but that seems a bit cheesy, to install only to remove later. That said, I think my suggestion has merit in its own right, seems like it would be user friendly feature... if you decide to implement it.

---

<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:** [7 January 2026 09:57 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053/4 "2026-01-07T09:57:13Z")

</div>

> [@Jibun-no-Kage](#):
>
> I think my suggestion has merit in its own right

Yes, I agree that there is merit in the ability to run if all unknown nodes are disabled. I don't know whether it would be complex to implement.

---

<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:** [7 April 2026 09:57 UTC](https://discourse.nodered.org/t/feature-request-if-a-flow-has-unknown-nodes-is-disabled-do-not-stop-all-flows/100053/5 "2026-04-07T09:57:16Z")

</div>

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