Comfy-Org / Comfy-Org/ComfyUI_frontend
Subgraph input bug
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 699
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 490
Description
### Custom Node Testing
- [ ] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)
### Expected Behavior
Hello! I create workflows and the subgraph is realy convenient and useful function. But I notice a bug when the same worflow works different for other users. A lot of them note that subgraph inputs are messed up and doesn't work. And they have certainly updated ComfyUI and other nodes but it didn't help. I tried to configure subgraph inputs different ways as connnect nodes to inputs or make hidden parameters visible and that didn't help either. Main issue is that subgraph parameters order is lost for different user with about the same ComfyUI configuration. Also there is issue than subgraph parameters show wrong values and so the workflow gives an error. Please help me resolve this problem! Screenshots with set subgraph and subgraph with messed up parameters in the same workflow from other user in attachment.
### Actual Behavior


### Steps to Reproduce
In this worflow I use custom nodes. And unfortunately I can’t do without them to create an adequate workflow.
[Friendly Qwen Image Edit 1.0b (GGUF).json](https://github.com/user-attachments/files/23766719/Friendly.Qwen.Image.Edit.1.0b.GGUF.json)
### Debug Logs
```powershell
There is usually no bug in terminal logs except any node loading errors beacuse of subgraph parameters messed up
```
### Other
_No response_
---
*This issue is transferred from: https://github.com/comfyanonymous/ComfyUI/issues/10909*
Original issue was created by @RuslanKuz at 2025-11-26T09:34:03.000Z
┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-6956-Subgraph-input-bug-2b76d73d365081be958ed5e8c62c8280) by [Unito](https://www.unito.io)
Contributor guide
Assessment
This issue has not been assessed yet.