Repository navigation
Catch, Status and Complete nodes do not show configuration error notification if attached to 0 nodes. #5875
Description
Current Behavior
Add a Catch, Status or Complete node to the flow and attach it to 0 nodes.
The node does not show the config error warning.
If the node is given a name there is no way of knowing that it is not connected without opening it.
This can easily happen if the node is initially attached and the attached node is deleted, and possibly even recreated. This can lead to confusion as it appears that the node is not generate errors (or whatever).
Expected Behavior
The node should show the warning triangle.
Steps To Reproduce
No response
Example flow
Environment
- Node-RED version: 5.0.1
- Node.js version: 24
- npm version:
- Platform/OS: Ubuntu
- Browser: Brave
Activity
Steve-Mcl commentedon Jul 16, 2026
For consideration - when the name is set there are ZERO UI cues to tell you what a catch|status|complete node is doing at all - meaning you must open it and check. I have been caught out by this in the past. Perhaps we might consider including a status on the node e.g. "Catch: all", "Catch: group", "Complete: 3", "Status: 1" etc?
colinl commentedon Jul 16, 2026
That could be useful, yes, but I don't think it negates the need for a config error notification.