Telemetry Top ComfyUI Errors in Wonderful Launcher
A production-facing summary of high-volume ComfyUI issue families observed in Wonderful Launcher telemetry, with the latest June 25, 2026 missing-module snapshot.
This report summarizes high-volume issue families from Wonderful Launcher production telemetry. The newest reviewed snapshot was checked on June 25, 2026; the older April 17 list remains below as a historical top-ten view.
These counts show event volume, not just unique users, so the biggest buckets are useful for prioritization but should still be interpreted carefully.
What this page is good for
This page is not a single-fix runbook. It helps answer a different question:
"Which ComfyUI failures are common enough that I should check a known guide first?"
Use it when:
- you are comparing multiple possible failure families
- you want to see which issues are recurring in real launcher usage
- you need a shortcut from a noisy log to a higher-confidence troubleshooting page
Latest snapshot: June 25, 2026
The clearest runtime signal in the June 25 review was missing Python modules:
- 30 days:
module_not_foundproduced 5,676 events across 53 installs. - 7 days:
module_not_foundproduced 1,230 events across 21 installs. - 30 days:
python_oomproduced 10 events across 5 installs. - 30 days:
cuda_oomproduced 8 events across 4 installs.
Top missing modules in the last 7 days:
| Missing module | Events | Installs | Start here |
|---|---|---|---|
triton | 394 | 15 | ComfyUI No Module Named triton |
sageattention | 81 | 7 | SageAttention Missing in ComfyUI |
onnx | 54 | 4 | ONNX or onnxruntime Missing in ComfyUI |
onnxruntime | 17 | 3 | ONNX or onnxruntime Missing in ComfyUI |
flash_attn | 13 | 3 | Fix No module named errors in ComfyUI |
llama_cpp | 10 | 3 | llama_cpp Missing in ComfyUI |
groundingdino | 8 | 3 | Fix No module named errors in ComfyUI |
nunchaku | 5 | 2 | ComfyUI Nunchaku Missing |
What changed in the June review
The most useful current content and product work is an accelerator/dependency cluster, not a generic "install every missing package" flow. triton, sageattention, flash_attn, llama_cpp, and nunchaku need diagnosis that considers Python, Torch, CUDA, platform, GPU architecture, and trusted wheel sources.
Some triton and sageattention lines can be optional acceleration warnings rather than fatal startup blockers. If ComfyUI reaches the ready state, do not treat every missing acceleration backend as an emergency. If a workflow or custom node cannot load, use the linked guide for that exact module.
Agent case reviews are useful for a different question: whether the AI repair loop chose the right tools, verified the fix, and avoided false success. Telemetry is the better source for how often users hit a runtime problem.
June 28 case-review follow-up
The latest Agent-case review added a second signal: many repairs failed not because the final fix was unknown, but because the workflow moved through several different failure stages.
That produced these public doc updates:
| Case pattern | Public page updated | What changed |
|---|---|---|
| Missing nodes install fails before cloning or downloading | ComfyUI Missing Nodes | Added Git/PATH, permission, clone/network, Manager registry, plugin import, and missing-model handoff branches |
| Custom-node install blocked by Git, PATH, proxy, or corrupt folders | Install ComfyUI Custom Nodes | Added a clone-failure table and clearer boundary between plugin files and Python packages |
| Manager cannot fetch the node registry while workflows still run | Failed to Get Custom Node List | Linked the registry failure path back to missing-node repair without treating it as a full ComfyUI reinstall problem |
Package field receives pip install ... or requirements.txt as text | Fix No module named errors and ONNX/ONNXRuntime Missing | Clarified package name vs pip command vs requirements file inputs |
| Nodes are fixed but model files are still missing | Where to Put Safetensors in ComfyUI | Added a missing-node-to-missing-model handoff so users do not mark a workflow as fixed too early |
| OOM diagnosis mixes VRAM, RAM, page file, and Python allocator failures | CUDA Out of Memory in ComfyUI | Added a memory-pool classifier before package or reinstall advice |
The pattern to keep is: one reviewed case cluster should usually update an existing troubleshooting page and one Agent/product rule. It should not become one thin article per badcase.
Historical top-ten snapshot: April 17, 2026
- Missing Plugin Module Warning Is Not Always Fatal - 5,159 events across 76 installs
- ComfyUI No Module Named 'triton' - 919 events across 97 installs
- SageAttention Missing in ComfyUI - 297 events across 35 installs
- InsightFace Missing in ComfyUI - 255 events across 12 installs
- Piexif Missing in ComfyUI - 135 events across 15 installs
- pkg_resources Missing in ComfyUI - 92 events across 9 installs
- HuggingFace HttpRequestException During Model Download - 36 events across 12 installs
- Deployment Failed While Downloading the Resource Package - 23 events across 20 installs
- Deployment Failed While Installing ComfyUI-Manager - 23 events across 16 installs
- Python Out of Memory in ComfyUI - 20 events across 8 installs
What mattered most in the April snapshot
- The biggest telemetry bucket was missing-module noise from plugins and optional backends.
- The biggest user blockers were deployment failures and download failures.
- A smaller but important cluster involved Python-side memory exhaustion during real workflow execution.
Practical takeaway for search and support
If a user pastes one exact error string into search, the best first landing pages are usually:
- ComfyUI No Module Named
triton - SageAttention Missing in ComfyUI
- InsightFace Missing in ComfyUI
- Deployment Failed: Downloading the Resource Package
- Deployment Failed: Installing ComfyUI-Manager
- How to Fix CUDA Out of Memory Errors in ComfyUI
Also worth watching
Outside the top-ten cutoff, the same telemetry snapshot also showed CUDA out-of-memory incidents, HuggingFace 403 and IOException download failures, and a small but high-confidence XamlLoadException startup crash cluster.
Recent support-case addendum
A later support-case review on May 11, 2026 surfaced a different kind of signal: exact error names that users are likely to paste into search. These are not directly comparable with the event counts above, but they are useful for finding high-intent troubleshooting pages.
| Error family | Exact wording users may search | Guide |
|---|---|---|
| Nunchaku node import failures | NunchakuFluxLoraLoader, NunchakuFluxLoraStack, NunchakuFluxDiTLoader | ComfyUI Nunchaku Missing |
| Dependency conflicts | qwen-tts requires transformers==4.57.3, mediapipe requires numpy<2, sensevoice-onnx requires setuptools<=65.0 | ComfyUI Dependency Conflicts |
| OpenCV package drift | opencv-python-headless, opencv-contrib-python, No module named 'cv2' | OpenCV (cv2) Missing or Conflicting |
| MMCV install failures | pip install mmcv exited with code 1, No module named 'mmcv._ext' | ComfyUI MMCV Install Failed |
| Saved workflow assets | Custom validation failed for node image, Invalid image file | Save a Workflow in ComfyUI |
How to use this section
- Start with the error guide that matches the package name or deployment step in your log.
- If your launcher still reaches the ready state, treat missing-module warnings as suspect but not automatically fatal.
- If setup stops before first launch, prioritize the deployment and download guides first.
Best hub pages to start with
If you do not yet know which exact bucket your problem belongs to, start with:
- ComfyUI Startup Failed
- Fix No module named errors in ComfyUI
- How to Fix Missing Nodes in ComfyUI Workflows
Source References
- Wonderful Launcher first-party telemetry reviews queried on April 17, 2026 and June 25, 2026
- ComfyUI troubleshooting overview
- ComfyUI custom node troubleshooting guide
Start free with Wonderful Launcher if this affects your real ComfyUI environment. It keeps launcher-native repair, task logs, and runtime checks in one place; credits are only for image generation and metered tools.
Download Wonderful LauncherSee credit packagesDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.