mirror of
https://github.com/Comfy-Org/ComfyUI-Manager.git
synced 2026-11-05 07:47:25 +00:00
[GH-ISSUE #2032] [Bug/Oversight] Custom node suites are not picked up from subgraphs #849
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/ComfyUI-Manager#849
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LaVie024 on GitHub (Jul 26, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/2032
I am currently testing quite a large workflow at the moment that I intend to publish publicly, which currently I have a near-complete version here:
noobai txt2img wf v0.9.json
The issue however, is that I tested this on another install on ComfyUI. Practically almost all the custom nodes were able to be picked up (with an issue of giriss' comfy-image-saver suite being picked up instead of alexopus' comfy-image saver suite which causes an issue due to one node from alexopus' suite being used that doesn't exist on giriss'), however, I noticed that the widgets on the Detailer Models subgraph was not being picked up.
What it should look like, versus how it shows up on the other install:


And when I checked the subgraph on the new install:

Comfy-Manager does not identify that the impact-subpack is missing, not in the main workflow, or even in the subgraph itself. This is a flaw that the group nodes had that I thought would've been corrected with subgraphs. It should be easier to be able to detect missing custom node suites from subgraphs than from group nodes, so this issue ought to be addressed before subgraphs are made a part of future releases of the frontend that are listed in the requirements.txt of ComfyUI itself.
@christian-byrne commented on GitHub (Jul 26, 2025):
That's a great point, we should solve this.