Skip to content
,

ComfyUI Prompt Outputs Failed Validation: Every Variant Fixed

10–15 minutes
Woman in a cosy library corner holding a card reading MODELS, hook Failed validation? Fixed

You press Queue and ComfyUI refuses to start, showing a red box that says Prompt outputs failed validation, followed by a node name and something like Value not in list: ckpt_name: 'model.safetensors' not in [...]. Nothing ran yet, so nothing is broken.

ComfyUI checked the workflow before running it and found an input it cannot use.

The good news: the lines under the heading tell you exactly which node and which input failed. This guide explains every common variant (Value not in list, not in [], Required input is missing, return type mismatch, min/max values, missing class_type) and the fix for each one.

TL;DR

  • What it is: a pre-flight check. ComfyUI found an input it cannot use, so it stopped before running anything.
  • Value not in list: the workflow asks for a file you do not have (or have under another name). Put the file in the right models/ subfolder, press R to refresh, then re-pick it in the dropdown.
  • not in [] (empty list): ComfyUI sees no files at all in that folder. Wrong folder, wrong path in extra_model_paths.yaml, or the folder is empty.
  • Required input is missing: a socket on that node is not connected. Wire it up or bypass the node.
  • Return type mismatch: two linked nodes pass the wrong kind of data (for example MODEL into a CLIP input). Re-wire it.

New to ComfyUI? My ComfyUI beginner guide covers install, models, nodes and fixes in one place.

How to Read the Error

Before ComfyUI runs a workflow, it walks back from every output node (Save Image, Preview Image, Save Video and so on) and checks every input those outputs depend on. If any check fails, you get this message and the queue stays empty. A typical error looks like this:

Prompt outputs failed validation
CheckpointLoaderSimple:
- Value not in list: ckpt_name: 'juggernautXL_v9.safetensors' not in ['sd_xl_base_1.0.safetensors', 'v1-5-pruned-emaonly.safetensors']

Read it in three parts:

  • The node name (CheckpointLoaderSimple): which node failed. ComfyUI also outlines that node in red on the canvas.
  • The reason (Value not in list): what kind of problem it is. Find it in the table below.
  • The input and the details (ckpt_name: '...' not in [...]): which widget is wrong, what the workflow asked for, and what ComfyUI actually has. If you have more than 20 files in that folder, ComfyUI shortens the list to (list of length 57) instead of printing every name.

If several nodes fail, each one gets its own block. Fix them from top to bottom, then queue again.

The full log in the terminal window (or the console in ComfyUI Desktop) shows the same text, and sometimes a little more, such as the node ID number. That ID matches the number shown on the node when you turn on node ID badges in the settings.

Every Variant and Its Fix

Message after the node name What it means Quick fix
Value not in list: ckpt_name: ‘x’ not in [‘a’, ‘b’] File name in the workflow does not match any file you have Download it, or pick one of the listed files
Value not in list: … not in [] ComfyUI sees no files in that model folder Put files in the right folder, check extra_model_paths.yaml
Value not in list: sampler_name / scheduler / mode Option removed or renamed in a newer node version Re-pick the option in the dropdown
Required input is missing: images An input socket is not connected Connect it, or bypass the node
Return type mismatch between linked nodes A link carries the wrong data type Re-wire to the matching output
Value -1 smaller than min of 0 / bigger than max A number is outside the allowed range Type a value inside the range
Failed to convert an input value to a INT value Text or a float where a whole number is needed Enter a plain whole number
Node ‘X’ has no class_type, or Node ‘X’ not found Broken JSON, or a node that failed to load Install the missing node or re-export the workflow
Prompt has no outputs No output node in the graph (a separate error) Add Save Image or Preview Image

Fix 1: Value Not in List

This is by far the most common variant. It appears when you load a workflow made by someone else: their file names are baked into the loader nodes, and you do not have those exact files.

  1. Read the missing name. In 'juggernautXL_v9.safetensors' not in [...], the part in quotes is what the workflow wants. The list after it is everything ComfyUI found in that folder.
  2. Decide: download or substitute. If you need that exact model (for example a specific VAE or a Flux text encoder), download it. If any model of the same family will do, just pick one of the files in the list.
  3. Put the file in the right folder. A checkpoint goes in ComfyUI/models/checkpoints/, a LoRA in models/loras/, and so on. See the cheat sheet below.
  4. Refresh. Press R on the canvas (or use the refresh option in the menu) so ComfyUI rescans the folders. A restart also works.
  5. Re-select the file in the dropdown. This step is easy to miss. Refreshing does not change the widget; you still have to click it and pick the file.

Watch for these name traps:

  • Subfolders: if the workflow author kept LoRAs in loras/sdxl/, the value is sdxl\style.safetensors or sdxl/style.safetensors. Your file in plain loras/ will not match. Re-pick it from the dropdown, which shows your real path.
  • Windows vs Linux slashes: a workflow made on Windows stores \, one made on Linux stores /. Re-picking the file fixes this too.
  • Browser downloads that add (1): model (1).safetensors is not model.safetensors. Rename the file.
  • Wrong extension: a .safetensors.part or .crdownload file means the download did not finish. Download it again.

The ComfyUI Manager can also help here: its model manager lists many common models and installs them straight into the correct folder.

Fix 2: The Empty List, not in []

When the list after not in is empty, ComfyUI found no files at all for that loader. The model name does not matter yet; ComfyUI is looking in the wrong place, or the folder is empty.

  • Check the folder. Open the folder the loader reads from (for example models/vae/) and make sure the file is really there, directly or in a subfolder.
  • Check you edited the right install. Many people have two ComfyUI copies, such as the portable build and ComfyUI Desktop. Files dropped into one are invisible to the other. ComfyUI Desktop keeps models in the folder you chose during setup, not inside the app folder.
  • Check extra_model_paths.yaml. If you share models with Automatic1111, Forge or another tool, this file tells ComfyUI where to look. A typo in base_path, a wrong indent, or a folder name that does not match (for example Lora vs loras) gives an empty list. After you edit it, restart ComfyUI and read the start-up log: it prints each extra path it adds.
  • Check the folder name for custom loaders. Custom nodes often read their own folders, such as models/ipadapter/, models/clip_vision/, models/upscale_models/ or models/unet/ for GGUF files. The node’s GitHub page names the folder. Create it if it does not exist.

My ComfyUI model folders cheat sheet lists every folder, which loader reads it, and how to set up extra_model_paths.yaml line by line.

Fix 3: Custom Node Options Changed

Sometimes the failed input is not a file at all, for example:

KSampler:
- Value not in list: scheduler: 'align_your_steps' not in ['normal', 'karras', 'exponential', ...]

Dropdowns like sampler, scheduler, mode, precision or device are fixed lists. When a node update renames or removes an option, old workflows still store the old value. The fix:

  1. Click the widget and pick the closest option from the list.
  2. If the option should exist, update the node pack (Manager, then Update) and also update ComfyUI itself, since some options come from the core.
  3. If the newest version removed it, check the node’s GitHub releases. You can pin an older version through the Manager, but re-picking a supported option is usually the better long-term fix.

A related case: the workflow was built with a different node pack that uses the same node name. The Manager’s “Install Missing Custom Nodes” picks one, and its options may differ. Read the workflow’s notes to see which pack the author used.

Fix 4: Required Input Is Missing

VAEDecode:
- Required input is missing: vae

A socket that must be connected has no link. This happens after you delete a node, swap a loader, or load a workflow where a node failed to load and its links were dropped.

  • Find the red-outlined node and look for the input dot named in the error. Drag a link to it from the matching output (a VAE output to a vae input, and so on).
  • If the node is not needed (for example an unused upscaler branch), bypass it with Ctrl+B or delete it, and make sure nothing downstream still needs its output.
  • If the input fed from a custom node that shows red or as a missing node, fix that first. My import failed and missing nodes guide walks through it.

Fix 5: Return Type Mismatch

CLIPTextEncode:
- Return type mismatch between linked nodes: clip, received_type(MODEL) mismatch input_type(CLIP)

A link carries the wrong kind of data. The message says what arrived (received_type) and what the input needs (input_type). The new frontend usually stops you from making such links, so this mostly appears with old or hand-edited workflows, or after a custom node changed its outputs.

Delete the link and drag a new one from the output with the right type. For example, a CLIPTextEncode needs the CLIP output of the checkpoint loader, not its MODEL output. Reroute nodes can hide these mistakes, so follow the link back to its real source.

Fix 6: Value Smaller Than Min or Bigger Than Max

KSampler:
- Value -1 smaller than min of 0: seed

Number widgets have limits. A seed of -1 (which means “random” in some other apps) is not valid in ComfyUI; use a normal number and set “control after generate” to randomize instead. Other common cases are width or height beyond the node’s maximum, a denoise above 1.0, or steps set to 0.

For Failed to convert an input value to a INT value, the widget got text or a decimal where it needs a whole number. This usually comes from a primitive or a math node feeding a widget that was converted to an input. Check that node’s output type and value.

Fix 7: Missing class_type or Node Not Found

Node 'Load Image Batch' has no class_type. The workflow may be corrupted or a custom node is missing.
Node 'Load Image Batch' not found. The custom node may not be installed.

Older ComfyUI versions word the first one as Cannot execute because a node is missing the class_type property. Every node in the prompt that ComfyUI receives needs a class_type, the internal name of the node, and ComfyUI must have a node registered under that name. This fails when:

  • a custom node is not installed or failed to import, so the frontend cannot convert it;
  • you sent an API-format workflow by script and the JSON is broken or saved in the normal UI format instead of the API format;
  • the workflow file was truncated or hand-edited.

Install the missing nodes and restart. If you call ComfyUI from a script, export it with Workflow, Export (API) and send that file, not the normal save.

Model Folder Cheat Sheet

Most “Value not in list” errors are solved by putting a file in the folder its loader reads:

Loader node Folder under ComfyUI/models/
Load Checkpoint checkpoints/
Load Diffusion Model (UNET), Flux, Wan, Qwen-Image diffusion_models/ (older name: unet/)
Load CLIP, DualCLIPLoader, text encoders text_encoders/ (older name: clip/)
Load VAE vae/
Load LoRA loras/
Load ControlNet Model controlnet/
Textual inversion embeddings embeddings/
Load Upscale Model upscale_models/
Load CLIP Vision clip_vision/
Unet Loader (GGUF) unet/ or diffusion_models/

The full list, including IPAdapter, InstantID and video model folders, is in the model folders cheat sheet.

Prevent It Next Time

  • Keep the original file names from Hugging Face or Civitai. Most shared workflows use them.
  • Read the workflow’s notes first. Good authors list every model with a download link and folder.
  • Start from built-in templates (Workflow, Browse Templates). Recent ComfyUI versions show a missing-models dialog with download buttons for templates.
  • Keep one ComfyUI install, or share one models folder between installs with extra_model_paths.yaml.
  • Update nodes and ComfyUI together, so dropdown options stay in step.

If validation passes but the run then fails, the problem is elsewhere: see mat1 and mat2 shapes cannot be multiplied for mixed model families, CUDA out of memory for VRAM limits, or the full list of common ComfyUI errors and fixes.

FAQ

I put the model in the folder but still get Value not in list. Why?

Two usual reasons: you did not refresh (press R), or you refreshed but did not re-pick the file in the dropdown. Also check that the name matches exactly, including any subfolder.

Can I just ignore the error and run anyway?

No. ComfyUI will not queue a workflow that fails validation. Bypassing the failing node with Ctrl+B works only if nothing that leads to an output needs it.

Why does a workflow from Civitai always show this error?

Because it stores the author’s file names and folder layout. Re-pick each loader’s file from your own list, or download the exact models listed in the workflow’s notes.

Does this error mean my GPU or install is broken?

No. It happens before anything is sent to the GPU. It only means an input in the workflow is not valid for your setup.

What is the difference between this and “Prompt has no outputs”?

“Prompt has no outputs” means the graph has no output node at all, such as Save Image or Preview Image. Add one and queue again.

Sources

Free weekly email

Get new AI guides every week

One short weekly email with our newest local AI, ComfyUI and AI tool guides. No spam, no pop-ups, just the good stuff.

Free. Unsubscribe anytime in one click. We only use your email to send this newsletter. See our privacy policy.

Woman in a cosy library corner holding a card reading MODELS, hook Failed validation? Fixed