# Workspace contains some nodes that are not properly configured

**URL:** <https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238>\
**Category:** General\
**Created:** [2 March 2022 14:26 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238 "2022-03-02T14:26:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [2 March 2022 14:26 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/1 "2022-03-02T14:26:35Z")

</div>

I upgrade my flows to Node-Red 2.2.2  
Now I get this attached message.  
I cannot see any problems in the application. How can I identify the problematic nodes?

 ![Screenshot 2022-03-02 151800](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/7/073b4dad2385608442abb7ad7529f735d78ded43.jpeg)

---

<div class="post-metadata">

**Author:** ![edje11](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edje11/32/572_2.png) [@edje11](https://discourse.nodered.org/u/edje11)\
**Post date:** [2 March 2022 15:17 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/2 "2022-03-02T15:17:11Z")

</div>

Update your dashboard to \>= v3.1.6, then it should work again.

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [2 March 2022 19:53 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/4 "2022-03-02T19:53:00Z")

</div>

thanks, but I have already dashboard v3.1.6  
all components are up to date  
the problem still exists ☹

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [9 March 2022 22:31 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/5 "2022-03-09T22:31:14Z")

</div>

Same problem for me.  
Should I remove all spacers where 0 nodes use them  
I'm afraid to say but I do not know what a spacer is 😊

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [9 March 2022 22:57 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/6 "2022-03-09T22:57:10Z")

</div>

Yes you can safely remove them. This issue has been thoroughly discussed

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [9 March 2022 23:42 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/7 "2022-03-09T23:42:30Z")

</div>

Thoroughly discussed yes but @juntiedt has 173 of them and I don't recall anyone giving a way to get rid of them en masse nor prevent them recurring, beyond upgrading to the version he already has.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [10 March 2022 03:36 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/8 "2022-03-10T03:36:35Z")

</div>

Click on one. Ctrl-A, selects them all. Hit delete

The newest dashboard fixes the problem so it shouldn't happen again

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [10 March 2022 07:55 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/9 "2022-03-10T07:55:42Z")

</div>

> [@gerry](#):
>
> This issue has been thoroughly discussed

Could be, reading everyday here, but had no problems with ui\_spacers until I updated node-red.  
With a search I did not find an solution, only in this post someone else who had the same problem.  
When I do a ctrl-A a lot of the screen turns blue (using Vivaldi)  
I have made a fairly complex dashboard screen and I know that one "wrong" move destroys the complete layout.  
That's why I am being very cautious with changes in the UI department.  
Please direct me to one of the topics / pages that explain the removal of the offending

> The workspace contains some nodes that are not properly configured:

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [10 March 2022 09:01 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/10 "2022-03-10T09:01:27Z")

</div>

> [@yogy](#):
>
> I have made a fairly complex dashboard screen and I know that one "wrong" move destroys the complete layout.  
> That's why I am being very cautious with changes in the UI department.

Export your entire flow before you make any changes so you have a backup.

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [10 March 2022 09:38 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/11 "2022-03-10T09:38:21Z")

</div>

Hi Gerry,  
I went the hard way and deleted all spacer one by one. It seemed that there were less than shown in the alarm message.  
Unfortunately I had to redo 2 of my screens. One was very complex.  
This in mind, deleting all spacer with ctl A means you will certainly have some work in reconfiguring your screen layouts.

---

<div class="post-metadata">

**Author:** ![gerry](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gerry/32/21604_2.png) [@gerry](https://discourse.nodered.org/u/gerry)\
**Post date:** [10 March 2022 13:43 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/12 "2022-03-10T13:43:49Z")

</div>

In your case it seems it created additional heart ache. On my 5 pi's there was no impact on any dashboards.

[EDIT] searching for "spacer" turns up the threads about this

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [11 March 2022 15:07 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/13 "2022-03-11T15:07:43Z")

</div>

I'm very sorry to say that I do not know how to find the offending nodes or tabs or pages.  
Using node-red for 2 years now, never had this warning, appeared after an last update.  
Have a basic understanding of node-red and running my home automation with it, just simple only node-red as interface.

I just want to now how do I find where the "spacer x (ui\_spacer)" is.  
The warning is there, but there are far over the 100 uit\_spacers in the right side bar under different tabs , witch one are wrong, and what is wrong with them  
If I do not know what nodes are not properly configured, how can I make the configuration correct?  
Sorry to look like a lost soul, but I am.  
For me the warning reads **"there are lots of nodes wrong, have a nice day"**  
Not very helpful for me

> The workspace contains some nodes that are not properly configured:
> 
> - [unassigned] Settings (ui\_group)
> - spacer x (ui\_spacer)
> - spacer x (ui\_spacer)
> - spacer x (ui\_spacer)
> - spacer x (ui\_spacer)
> - 
> - 24 more
> 
> Are you sure you want to deploy?

---

<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:** [11 March 2022 15:36 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/14 "2022-03-11T15:36:06Z")

</div>

> [@yogy](#):
>
> I just want to now how do I find where the "spacer x (ui\_spacer)" is.

Have you tried CTRL+F

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/f/ff1f30b9db56875597e2c30953ad34388b91cf61.png)

Have you looked in unused config nodes  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/7/775317e8714b0852c55d7a55d09451e9c7bca9b8.png)

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [11 March 2022 16:06 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/15 "2022-03-11T16:06:49Z")

</div>

> [@Steve-Mcl](#):
>
> Have you looked in unused config nodes

Yes there are a lot "spacer x" an a lot of spacer 1x1 6x1 2x1 etc  
But I see no warning of some kind that gives a clue.  
Unused mean I must delete them?.  
And my careful crafted complex dashboard wil not end in a mess?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [11 March 2022 16:17 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/16 "2022-03-11T16:17:47Z")

</div>

Copy your carefully crafted complex flows before you mess with them!

Of course you have regular and robust backups. Don't we all? 😊

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [11 March 2022 16:34 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/17 "2022-03-11T16:34:30Z")

</div>

We have, as usual, reading this board for 2 years, besides other software boards.  
And we are after 40+ years working with computers not completely ignorant about backups.  
So procedure :  
copy flow,  
remove a spacer,  
deploy,  
check your dashboard carefully,  
rinse and repeat.

Looks very tedious task.  
And if you remove all in once and check you wil not know witch spacer you better had left untouched.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [11 March 2022 16:37 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/18 "2022-03-11T16:37:06Z")

</div>

Yes, imho it's a serious and hard to reproduce bug, let's hope it has been successfully squashed with the latest NR and dashboard releases.

---

<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:** [11 March 2022 20:26 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/19 "2022-03-11T20:26:09Z")

</div>

> [@yogy](#):
>
> Looks very tedious task.  
> And if you remove all in once and check you wil not know witch spacer you better had left untouched.

However that test will only take two minutes to do and you may find that the layout is only slightly messed up, so it is worth trying that first. You can always go back to the original flow to start again.

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [11 March 2022 20:32 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/20 "2022-03-11T20:32:36Z")

</div>

> [@Colin](#):
>
> However that test will only take two minutes to do and you may find that the layout is only slightly messed up, so it is worth trying that first.

And that's how I will proceed this weekend. 😟

---

<div class="post-metadata">

**Author:** ![yogy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/yogy/32/32191_2.png) [@yogy](https://discourse.nodered.org/u/yogy)\
**Post date:** [13 March 2022 14:34 UTC](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238/21 "2022-03-13T14:34:03Z")

</div>

> [@Colin](#):
>
> You can always go back to the original flow to start again.

Managed it in 2 hours and 5 restarts.  
Removed things I never made, or knowing what they did.  
Just a sort of pavlov editing, this is spacer x so remove.  
No joy for one who likes to know why he is doing something, I have to less knowledge of the inners of node-red/dashboard.

[Next page](https://discourse.nodered.org/t/workspace-contains-some-nodes-that-are-not-properly-configured/59238.md?page=2)