"Unsupported Nodes" are not marked red
Custom Node Testing
- [ ] I have tried disabling custom nodes and the issue persists (see how to disable custom nodes if you need help)
Expected Behavior
After a recent ComfyUI update I get the error:
"Workflow contains unsupported nodes (highlighted red). Remove these to run the workflow."
Among the affected nodes are ComfyUI-GGUF nodes, KJNodes and comfyui_controlnet_aux nodes, which are essential for my workflow and system.
Affected nodes should be marked red (as stated in the error message)
Actual Behavior
Affected nodes are not marked red (as stated in the error message). Tested in Firefox 144.0.2 and Chromium 139.0.7258.154
Steps to Reproduce
Any workflow with added GGUF nodes or KJNodes.
Debug Logs
My System:
AMD Ryzen 8700G
Debian 13
Total VRAM 47285 MB, total RAM 47285 MB
pytorch version: 2.10.0.dev20251002+rocm7.0
Set vram state to: DISABLED
Device: cpu
Using pytorch attention
Python version: 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0]
ComfyUI version: 0.3.70
ComfyUI frontend version: 1.33.4
[DEPRECATION WARNING] Detected import of deprecated legacy API: /extensions/core/widgetInputs.js. This is likely caused by a custom node extension using outdated APIs. Please update your extensions or contact the extension author for an updated version.
[DEPRECATION WARNING] Detected import of deprecated legacy API: /scripts/ui.js. This is likely caused by a custom node extension using outdated APIs. Please update your extensions or contact the extension author for an updated version.
Other
No response
This issue is transferred from: https://github.com/comfyanonymous/ComfyUI/issues/10822
Original issue was created by @whitespace-rebel at 2025-11-21T04:53:21.000Z
┆Issue is synchronized with this Notion page by Unito
This is a known issue in the current ComfyUI frontend: while the error message says unsupported nodes should be "highlighted red," the actual red marking is not applied to those nodes on the canvas. Recent frontend updates added warning icons and tooltips about unsupported nodes, but the logic that visually marks these nodes red is either missing or not properly connected to the node rendering system. The detection of unsupported nodes happens at the workflow level, but this information isn't forwarded to the node components that control the red border or error state, which is why you don't see the expected highlighting—even though the UI warns you about unsupported nodes and disables the Run button source.
This appears to be a regression or oversight introduced in recent updates. There is no indication that your custom node deprecation warnings are directly responsible, especially since the issue persists with all custom nodes disabled. For now, the only indicators for unsupported nodes are the warning icon and tooltip on the Run button and workflow breadcrumbs, not the red highlight on the nodes themselves.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Okay, this seems to be pretty much a duplicate of https://github.com/Comfy-Org/ComfyUI_frontend/issues/6766 This issue can be closed.
v1.33.5 fixed the button being disabled for me, but there still are "⚠️" icons on the workflow name and the run button saying there are unsupported nodes highlighted in red, when there are no invalid nodes and the workflow runs just fine.
No idea if this is related, but there are some warning like: [DEPRECATION WARNING] Detected import of deprecated legacy API: /scripts/ui/components/button.js in the log, though it doesn't tell me which custom nodes are using those.
@KrsityKu @whitespace-rebel Could you send me your workflow so I can try to reproduce the issue on my side?
So just to confirm, the symptoms are:
- You see a warning icon saying there are missing nodes.
- But there are no missing nodes with a red outline in the workflow.
- And the workflow still runs fine.
Is that correct?
So just to confirm, the symptoms are:
- You see a warning icon saying there are missing nodes.
- But there are no missing nodes with a red outline in the workflow.
- And the workflow still runs fine.
Is that correct?
I can confirm that at some point I was seeing exactly that (warning icon, no missing nodes, Run button working) with frontend 1.33.5 (I think). But I can't see that any more. Might be because I have the "nasty" habit to delete from time to time comfy.settings.json file in ComfyUI\user\default folder to reset everything to default and redo my settings again. I'm not sure though when the disappearance of the warning icon happened, I didn't pay much attention to it as long I could run my prompts.
Edit: Funny enough, I actually DO have a missing node in my current workflow that I have now open and there is no warning (not that I would care about such warning, the node is bypassed anyway). It was though a proper warning displayed when I opened the workflow.
@viva-jinyi here is a workflow that did not run at all in version 1.33.4 (Run button was not clickable):
As long as GGUF nodes or KJNodes or comfyui_controlnet_aux nodes are in the workflow, the Run button remains unclickable. So I thought if there is a problem with these custom nodes, they should at least be highlighted red. But if there is no problem with these custom nodes, then there should be no error message.
As @KrsityKu discovered, with version 1.33.5 the Run button is clickable again, even with those custom nodes present,
but the error message "Workflow contains unsupported nodes (highlighted red). Remove these to run the workflow." is still there, and the affected nodes are not highlighted red.
Version 1.34.0 fixed the issue for me. No error messages, and custom nodes just work. Thank you!
EDIT: The error message returned after a few days, but then disappeared again. The Run button works.
EDIT_2: Pressing R makes the error message pop up again.
Just here to say I see this too. I moved all the nodes around in search of those "red nodes". None found so far. I even cloned the WF and then deleted everything . I still see the warning on the empty workflow!
PS: I changed the requirements from comfyui-frontend-package==1.32.9 to comfyui-frontend-package==1.34.2 So far it works. But the latest ComfyUI pull still wants 1.32.9.