Using subgraphs can lead to nodes with duplicated badge numbers

[JorgeR81]

Prerequisites

• I am running the latest version of ComfyUI
• I have searched existing issues to make sure this isn't a duplicate
• I have tested with all custom nodes disabled (see how)

What happened?

Using subgraphs can lead to nodes with duplicated badge numbers.

Steps to Reproduce

1. Open the default workflow.
2. Create a subgraph with KSampler and VAE Decode
3. The subgraph badge number will be 10
4. Inside the subgraph, add another node, and the badge number it's also 10

How is this affecting you?

Feature doesn't work as expected

ComfyUI Frontend Version

Tested with 1.26.13 and 1.28.5 ( latest )

Browser

Chrome/Chromium

Console Errors

Logs

Additional Context

No response

┆Issue is synchronized with this Notion page by Unito

[dosubot]

This is a known limitation in the current ComfyUI frontend architecture. Each subgraph (and the main graph) manages its own node IDs independently, so badge numbers can be duplicated between nodes in different graph scopes. The frontend displays badge numbers based on these per-graph node IDs, without enforcing uniqueness across all graphs and subgraphs. This is a structural aspect of how node IDs are assigned and displayed, not a bug in your setup or workflow. Maintainers have acknowledged that subgraph features, including node ID and linking behavior, are under active development and will be improved in future updates, but there is no fix or workaround available yet for badge number duplication in subgraphs. For more details, see the related discussion and maintainer comments here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[AustinMroz]

This is functioning as intended. nodeIds are unique per graph. Internally, referencing nodes across graphs is done either with locatorIds ([subgraphUUID:]nodeId) or executionIds ([...parentSubgraphNodeId:]nodeId).

Is this causing problems?

[JorgeR81]

For me this behavior it's not a problem.
You can close this issue, if you don't need to change the way it works.

( I just noticed this, because of the new method to promote widgets. )