# Deploy with improperly configured nodes
**URL:** https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464
**Category:** Feature Requests
**Tags:** editor
**Created:** [17 February 2025 12:06 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464 "2025-02-17T12:06:14Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [17 February 2025 12:06 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/1 "2025-02-17T12:06:14Z")
When you do a deploy, even only of modified nodes, Node-red checks all flows for nodes not properly configured. Of course this is essential, a badly configured node might be accessed by a link from the current flow, or it may be a config node not visible on any flow.
Is it possible to ignore improperly configured nodes which are on a disabled tab?
For example, I have a tab with dashboard v1 nodes.
The tab is disabled and it's dashboard page(tab) is deleted but I want to retain the nodes for reference.
Now I'm working on an unrelated flow and a deploy brings up irrelevant warnings
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [17 February 2025 12:31 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/2 "2025-02-17T12:31:47Z")
In fact the deployment should ignore them, I'll investigate.
Ok, only works if the node is disabled - will fix that 😉
---
### Author:  [@omrid](https://discourse.nodered.org/u/omrid)
#### Post date: [17 February 2025 12:45 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/3 "2025-02-17T12:45:35Z")
I fully fully concur with this, and would also add another related request:
Today, when I deploy, if there are unused configuration nodes I get a warning. While I can see the value in warning against accumulating garbage, sometimes I may want to have a set of configuration nodes (e.g. DB connections) of which only one is concurrently active, and would not want to get warned of unused config nodes who are disabled
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [17 February 2025 13:00 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/4 "2025-02-17T13:00:50Z")
> [@omrid](#):
>
> I may want to have a set of configuration nodes (e.g. DB connections) of which only one is concurrently active, and would not want to get warned of unused config nodes who are disabled
100% if a node or config is badly configured AND is disabled, I don't want to be bugged every time. I disabled it for a reason.
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [17 February 2025 13:02 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/5 "2025-02-17T13:02:20Z")
Agreed.
>
>
> \## Types of changes
>
> \- \[x\] Bugfix (non-breaking change which fixes an issue)
> …- \[\] New feature (non-breaking change which adds functionality)
>
> \## Proposed changes
>
> Ref: https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464.
>
> Ignore invalid nodes and unused config nodes if they are disabled or the parent flow is disabled.
>
> \## Checklist
>
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[x\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [17 February 2025 13:18 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/6 "2025-02-17T13:18:24Z")
Thanks @GogoVega 👍
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 February 2025 15:09 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/7 "2025-02-17T15:09:12Z")
Can one disable a config node?
---
### Author:  [@GogoVega](https://discourse.nodered.org/u/GogoVega)
#### Post date: [17 February 2025 15:15 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/8 "2025-02-17T15:15:20Z")
Of course, config nodes like nodes can be disabled.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 February 2025 17:07 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/9 "2025-02-17T17:07:59Z")
Oh yes, back at my computer I see that you can.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [18 April 2025 17:08 UTC](https://discourse.nodered.org/t/deploy-with-improperly-configured-nodes/95464/10 "2025-04-18T17:08:57Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.