Isolate custom-node conflicts with a reproducible baseline and binary search

Purpose and scope

Replace random uninstalling with controlled groups and repeatable input. The goal is the smallest triggering set, not a blanket verdict on all third-party nodes.

Source-supported context

Official troubleshooting distinguishes frontend-extension isolation from backend-node isolation and describes bisecting. Disabling code does not reverse dependency changes made during installation. Source 1 Source 2

Before you start

1. Save the original workflow, versions, launch options and installed-node list.

2. Choose a minimal request that reproduces the issue consistently with the same input.

3. Prepare separately for disabling code and restoring the Python environment.

Steps and checks

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Identify whether the first failure is in the browser or Python. Start with the corresponding extension controls or startup logs.

Step 2. Temporarily disable the relevant frontend extensions or backend custom nodes using the current supported method, then test a baseline without those components.

Step 3. If the baseline works, restore components in groups and record each result. Reload the frontend after frontend-only toggles, or restart ComfyUI after backend-node changes; check whether a pair rather than one package triggers the conflict.

Step 4. If disabling code does not help, compare the changed dependencies with a clean environment. Consult candidate projects' issues/migration notes before choosing an update or rollback.

Completion check

A minimal difference between failing and passing environments is recorded with nodes, versions and input, suitable for a maintainer report.

Limitations and cautions

Cache, randomness and resource pressure can affect one-off results. Repeat tests and do not declare temporarily non-triggering packages universally safe.

Original sources

• ComfyUI custom node troubleshooting — original record checked 2026-09-21.
• How to update ComfyUI — 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

• Blank ComfyUI screen after an extension update: separate frontend and backend failures
• Cannot import name after an update: check the importing code and dependency together
• Back up before updating ComfyUI: a source rollback is not an environment rollback