Telemetry Top 10 ComfyUI Errors in Wonderful Launcher
A production-facing summary of the ten highest-volume issue families observed in the telemetry snapshot queried on April 17, 2026.
This report summarizes the ten highest-volume issue families in the production telemetry snapshot queried on April 17, 2026. It is meant to help users and support operators separate noisy warnings from the problems that most directly block setup and workflow success.
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
Top 10 issue families
- 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 matters most
- 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 snapshot queried on April 17, 2026
- ComfyUI troubleshooting overview
- ComfyUI custom node troubleshooting guide
Start with Wonderful Launcher if this issue touches your real ComfyUI environment. Use the docs to understand the fix, and use the app to inspect the machine you already have.
Download Wonderful LauncherDid this fix your issue?
Your answer helps prioritize verified ComfyUI repairs.
Resource Package Download Failed
How to fix deployment failures during the resource package download step when setting up ComfyUI, especially when GitHub downloads time out or your proxy path is incomplete.
No Module Named
Diagnose ComfyUI ModuleNotFoundError and No module named errors by package name, Python environment, custom node dependency, and CUDA or PyTorch mismatch.