Start with the problem in front of you.

Distinguish full and lite distributions, source-build failures and runtime extension loading.

A successful installation in a terminal does not show that ComfyUI uses the same Python. Separate the import name, distribution name and running interpreter before changing dependencies.

These messages usually concern the interface between NumPy and a compiled extension, not a broken workflow connection. Locate the first implicated extension before changing NumPy.

Check the wheel tags and keep the ComfyUI extension, native library and model separate.

The import may belong to a node-specific wrapper or native SDK binding. One log line does not identify a trusted, compatible distribution on a package index.

Separate package discovery, runtime providers and the session that actually executes your model.

Identify the installed OpenCV flavor before investigating missing modules or native-library loading.

Diagnose the failing hostname, certificate chain and interpreter before treating HTTPS verification as an inconvenience to bypass.

pip needs a candidate compatible with the requested package/version, Python, operating system, architecture and configured index. No candidate does not necessarily mean that the project does not exist.

Dependency resolution failures mean pip could not satisfy the requested constraints. Separate a real conflict from slow backtracking, timeouts and certificate failures before retrying.

Older generated Python message code can conflict with its runtime. Locate the package carrying that code before changing every Protobuf consumer in the environment.

Rendering nodes can depend on a Python binding, an acceleration extension and a usable graphics context. Locate the failing layer before changing packages or graphics settings.

Check library availability before investigating DNS, TLS, HTTP responses or timeouts.

Understand cache placement and storage precision as separate controls from model-file quantization.

Document the core class and its input/output contract without confusing UI capacity with model support.

Check exact class names and graph definitions before treating an embedded subgraph UUID as a missing extension.

Separate the node wrapper's requirements from those of the Qwen TTS distribution. A precise project pin is not a recommended shared version for every model.

A missing positional-encoding implementation is not a missing weight file. Once import works, inspect the API and tensor contract used by the actual model.

Distinguish the Python library from the weight file before reinstalling packages or downloading models again.

A missing Python module, a missing Triton dependency and a Windows _fused DLL failure occur at different layers. Upgrading every dependency together is not a targeted repair.

Keep the precise import and operation errors instead of treating every scientific-library failure as an install issue.

Identify the implementation required by the node before replacing segmentation packages or checkpoints.

A historical setuptools constraint is not a reason to downgrade the whole environment. Establish the installed release and whether the error concerns building or runtime dependencies.

Check the dependency first, then the expression and allowed operations exposed by the node.