Comfy-Org / Comfy-Org/ComfyUI_frontend

Latest updates broke every workflows. I feel guilty.

Open
#9,975 1 comment 0 reactions 0 assignees View on GitHub
area:subgraph Potential Bug
Dominant language
TypeScript
Stars
2k
Forks
704
Avg merge
1d 8h
Merged PRs (30d)
512

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

Previous workflows to keep working (retro compatibility)

### Actual Behavior

Every subgraph is broken.

### Steps to Reproduce

Just trying to run.

### Debug Logs

```powershell
Not needed.
```

### Other

I think I've found a solution to avoid these kinds of anomalies/problems. I used AI to recreate my subgraphs as custom nodes.

This way, updates probably won't impact workflows.

But I think it's problematic that we have to resort to these kinds of solutions to keep working.

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-9975-Latest-updates-broke-every-workflows-I-feel-guilty-3246d73d365081668187fb8d90e4805d) by [Unito](https://www.unito.io)

Contributor guide

Open the contributing guide

Research direction

The report names no files, tests, workflow, or useful debug logs, so start by reproducing the failure with a specific workflow and inspect which subgraph breaks after the latest update. Narrow the regression to a reproducible compatibility case. Done means previously working workflows run successfully again without requiring custom-node rewrites.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.