Skip to content

fix: improve error message when node type is missing#12194

Merged
comfyanonymous merged 1 commit intomasterfrom
COM-12528-improve-missing-node-error
Feb 1, 2026
Merged

fix: improve error message when node type is missing#12194
comfyanonymous merged 1 commit intomasterfrom
COM-12528-improve-missing-node-error

Conversation

@christian-byrne
Copy link
Contributor

Background

Currently, users (especially new users or users who don't know about custom nodes) will often execute workflows they got from someone else that contain nodes they do not have installed. The error message they receive is very technical and doesn't really convey what the underlying problem most likely is. This PR addresses the issue by adding a specific error type so the frontend can open a dialog with guided resolution steps (using existing dialog for "missing nodes error"). It also improves the error message content for people using other frontends, headless, or who have not updated their frontend.

Here is a list of all issues I could find where the user got the current error message and didn't understand how to resolve the issue (and/or believed it was an actual bug in ComfyUI):

- Change error type from 'invalid_prompt' to 'missing_node_type' for frontend detection
- Add extra_info with node_id, class_type, and node_title (from _meta.title)
- Improve user-facing message: 'Node X not found. The custom node may not be installed.'

Fixes COM-12528

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019c0df1-aa57-72e0-8193-46aa24b5a327
@notion-workspace
Copy link

@christian-byrne christian-byrne added the Core Core team dependency label Jan 31, 2026
@comfyanonymous comfyanonymous merged commit 32621c6 into master Feb 1, 2026
16 checks passed
@comfyanonymous comfyanonymous deleted the COM-12528-improve-missing-node-error branch February 1, 2026 06:13
simonri pushed a commit to simonri/ComfyUI-flash-attention-3 that referenced this pull request Feb 2, 2026
- Change error type from 'invalid_prompt' to 'missing_node_type' for frontend detection
- Add extra_info with node_id, class_type, and node_title (from _meta.title)
- Improve user-facing message: 'Node X not found. The custom node may not be installed.'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Core Core team dependency

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants