# Feature request: start flow despite unregistered nodes if they are disabled

**URL:** <https://discourse.nodered.org/t/feature-request-start-flow-despite-unregistered-nodes-if-they-are-disabled/51831>\
**Category:** General\
**Created:** [4 October 2021 11:44 UTC](https://discourse.nodered.org/t/feature-request-start-flow-despite-unregistered-nodes-if-they-are-disabled/51831 "2021-10-04T11:44:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![heleon19](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/heleon19/32/48971_2.png) [@heleon19](https://discourse.nodered.org/u/heleon19)\
**Post date:** [4 October 2021 11:44 UTC](https://discourse.nodered.org/t/feature-request-start-flow-despite-unregistered-nodes-if-they-are-disabled/51831/1 "2021-10-04T11:44:50Z")

</div>

If a node type is not present in a flow, the entire flow will not start.  
This restriction is quite reasonable, but sometimes tedious when switching between different projects.

My suggestion: If a node is deactivated, or if a tab "Flow" is deactivated, these unknown nodes should be ignored. This way the project would still be executed.

---

<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:** [3 December 2021 11:45 UTC](https://discourse.nodered.org/t/feature-request-start-flow-despite-unregistered-nodes-if-they-are-disabled/51831/2 "2021-12-03T11:45:20Z")

</div>

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