diagnose_run
Identify why a ComfyUI render failed: returns the error, missing models, and missing node types from any failed run.
Instructions
WHY DID MY RENDER FAIL / WHAT'S MISSING? Explains a failed run in ONE call, without needing a canvas — the headless counterpart to the panel's panel_view_errored_nodes ("why is this red?"), so mobile/remote sessions get the same answer. Returns: the failed node (id, type) with its exception_type + message and a trimmed traceback; missing_models (the exact model file that isn't installed and the widget holding it — feed the filename to search_civitai_models/download_model to fix it); missing_node_types (node classes this install lacks — feed to search_custom_nodes/install_custom_node); and any other per-input validation errors. Call this whenever a run fails, an enqueue is rejected, or the user asks what's missing — instead of guessing from raw logs. With no prompt_id it diagnoses the most recent FAILED run (falling back to the most recent run). Read-only.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prompt_id | No | Specific run to diagnose (the prompt_id from enqueue_workflow). Omit to diagnose the most recent FAILED run — preferred over a newer successful one — falling back to the most recent run if nothing failed. |