Prepare a useful, redacted ComfyUI error report

Purpose and scope

The last line of a screenshot rarely identifies the instance, input and first exception. Preserve a complete local record and share a deliberate redacted report.

Source-supported context

Official troubleshooting asks for logs, and API validation supplies structured node_errors. Startup, request validation and runtime failures should be recorded as distinct stages. Source 1 Source 2 Source 3

Before you start

1. Retain the original log locally and make a separate sanitized copy for sharing.

2. Review prompts, images, paths and external resource references before making a workflow public.

3. Report one reproducible issue rather than mixing unrelated environments.

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. Record the stage—startup, import, validation, loading, sampling, decoding or saving—and the last known successful operation.

Step 2. Include installation type, OS, actual Python, Torch, core/frontend and relevant node versions, plus GPU and task dimensions.

Step 3. Preserve the first exception, technical class/node ID and relevant traceback while removing tokens, cookies, usernames, private URLs and unrelated logs.

Step 4. List minimal reproduction steps, attempted changes and their results, retaining before/after records. Do not call a one-off unrepeatable outcome a stable repair.

Completion check

Another reader can understand the problem without guessing basic environment facts and can distinguish observations, hypotheses and attempted remedies.

Limitations and cautions

Do not upload unreviewed full logs to public tools. The included templates contain no real user logs or credentials.

Original sources

• ComfyUI troubleshooting overview — original record checked 2026-09-21.
• ComfyUI custom node troubleshooting — original record checked 2026-09-21.
• ComfyUI Server API routes — 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

• Isolate custom-node conflicts with a reproducible baseline and binary search
• POST /prompt returns 400: inspect node_errors before retrying
• Back up before updating ComfyUI: a source rollback is not an environment rollback