Google holds 14% of Anthropic equity, with a total investment of over US$3 billion
640
English
English
When there is an error in the node, the status as shown in the figure below will be displayed. The outer frame will show a red stroke, and there will be a red circle prompt for the corresponding connection node, prompting that the connection point is not connected. The following is a three-step positioning + five-category high-frequency fault solution to facilitate everyone to solve the ComfyUI node error problem.
1. Red character positioning: Click the right click of the error node → Open Error Log , the core clue is usually in the last 3 lines (such as Shape mismatch [512×768] vs [512×512] )
2. Yellow word warning: WARNING prompts that the parameters are out of bounds (such as Sampler CFG=15 (max=10) ), and the valid range will be marked next to the value.
1. Troubleshooting of the broken line: Press and hold Alt to drag the canvas to check whether there are free ports (not connected gray triangle arrows)
2. Data type conflict: floating view port identifier (such as VAE node outputs Tensor , and cannot be directly connected to CLIP text encoder)
3. Resource black hole: CUDA OOM error is reported when the video memory is insufficient, try to enable --lowvram mode or reduce latent resolution
1.” ModuleNotFound ": Install missing nodes through ComfyUI-Manager (enter git clone [node warehouse address] /custom_nodes on the command line)
2." TypeError: float() argument must be a string... " : Check whether the numeric input box is mixed with Chinese symbols (such as "5" → "5" )
3. " Dimensional Mismatch ": Insert Latent Scaling Node in front of KSampler to force uniform size
Enable --force-fp16 running parameters, or right-click to select Toggle Bypass on the error-reported node and temporarily skip it, gradually narrowing the scope of the problem node. It is recommended to use Ctrl+D differential comparison of the workflow structure after saving the runnable version.
