Node has no class_type: distinguish API export errors from missing registration
An API execution node needs class_type. The same missing_node_type category may also report a class that exists in the request but is unknown to the backend, so read message and extra_info together.
Symptoms and scope
An API execution node needs class_type. The same missing_node_type category may also report a class that exists in the request but is unknown to the backend, so read message and extra_info together.
Error fragments for search; IDs, values and filenames may vary:
has no class_type
missing_node_type
Source-supported context
Core validate_prompt checks missing class_type separately from lookup in NODE_CLASS_MAPPINGS. Issues #6366 and #12105 contain related reports; an update helping one user does not justify nightly updates for everyone. Source 1 Source 2 Source 3
Cases to distinguish
1. A canvas UI JSON was submitted directly as an API prompt.
2. Export, manual editing or third-party conversion lost the node's technical type.
3. A frontend/node cannot serialize the graph correctly, or the backend has not registered its class.
Diagnostic sequence
The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.
Step 1. Confirm the file's purpose and inspect the failing node for inputs and class_type rather than only UI type, position and links.
Step 2. Re-export using the current version's supported API format from a workflow that opens correctly. Keep the original for comparison.
Step 3. If class_type already exists but is unknown, inspect /object_info and startup registration errors.
Step 4. Update only when a documented fix matches the node/version. Do not fill every missing type with KSampler or infer classes from display labels.
Completion check
The request contains valid types and passes server validation. Subsequent node_errors require their own specific checks.
Limitations and cautions
Editable display titles are not reliable Python class names. Format conversion needs the node's input semantics, not just field renaming.
Original sources
- ComfyUI execution.py validation — original record checked 2026-09-21.
- Node has no class_type — original record checked 2026-09-21.
- Missing class_type in custom node workflow — original record checked 2026-09-21.
Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.
Related troubleshooting and guides
Was this page helpful?
Anonymous. Only a yes/no counter is stored; no account, IP address or device details.
Sources & references
Localized from the existing Chinese research draft. Original source-check dates are retained; this translation is not new technical verification or a runtime test.
01ComfyUI execution.py validationSource checked: 2026-09-2102Node has no class_typeSource checked: 2026-09-2103Missing class_type in custom node workflowSource checked: 2026-09-21