unable to use Save Image node or Preview Image node

[CCJetWing]

Expected Behavior

I could save and preview the images a few days ago.

Actual Behavior

From yesterday onward after updated the nodes, it gives the following message:

Prompt outputs failed validation: Exception when validating node: name 'full_type_name' is not defined SaveImage:

• Exception when validating node: name 'full_type_name' is not defined

Steps to Reproduce

It works when I use Empty Latent Image node but error comes out when I use VAE Encode (for Inpainting) node and Set Latent Noise Mask node pairs.

Debug Logs

got prompt
Failed to validate prompt for output 9:
* (prompt):
  - Exception when validating node: name 'full_type_name' is not defined
* SaveImage 9:
  - Exception when validating node: name 'full_type_name' is not defined
Output will be ignored
invalid prompt: {'type': 'prompt_outputs_failed_validation', 'message': 'Prompt outputs failed validation', 'details': "Exception when validating node: name 'full_type_name' is not defined", 'extra_info': {}}

Other

No response

[huchenlei]

Have you tried disable all custom nodes? You can do that by passing --disable-all-custom-nodes flag

[ltdrdata]

The input name full_type_name is strange. Can you share your workflow?

[fyepi]

I have encountered the same problem. The images have been generated and could be found under output folder but they don't show up in preview node.

There is no error on console at all. The workflow is a most minimal one.

[fyepi]

It seems to be a browser compatibility issue. The problem happens on Edge on Ubuntu 22.04. When using chrome no such problems.

[kevinmarkwardt]

I do not think it's browser related, I am using Chrome and I have used this workflow for months with no trouble. I am getting this error after updating to the latest update of ComfyUI. Not changes to the workflow. Workflow is not using anything new. Weird thing is it is throwing errors on the save and preview image nodes. But those nodes work in another workflow where I am not using IPAdapter or Reactor. It seems to be something around those components. Also just tried without ControlNet and it was ok, added control net and errors.

`Prompt executed in 4.47 seconds got prompt Failed to validate prompt for output 787:

• (prompt):
  • Exception when validating node: name 'full_type_name' is not defined
• PreviewImage 787:
  • Exception when validating node: name 'full_type_name' is not defined Output will be ignored Failed to validate prompt for output 870:
• (prompt):
  • Exception when validating node: name 'full_type_name' is not defined
• PreviewImage 870:
  • Exception when validating node: name 'full_type_name' is not defined Output will be ignored 100%|██████████████████████████████████████████████████████████████████████████████████| 20/20 [00:04<00:00, 4.81it/s] Prompt executed in 4.50 seconds`

[kevinmarkwardt]

Did another test with the default workflow and add a couple ip adapter nodes and got the error.

[kevinmarkwardt]

Seems to be some sort of custom node that caused it. Started from a fresh comfy_ui and installed most of the custom nodes back and the issue is gone. I am good with closing this on my part.

[w1124c]

Hi. I was having the same problem, and after exploring the custom nodes one by one, it seems that the node {ComfyUI_ezXY} was doing something wrong, so I deleted it and the error disappeared.

[CCJetWing]

Hi. I was having the same problem, and after exploring the custom nodes one by one, it seems that the node {ComfyUI_ezXY} was doing something wrong, so I deleted it and the error disappeared.

I think I am having the same problem, after disabled the node, it remains normal, thank you.

[bitsentinel-cell]

Hi. I was having the same problem, and after exploring the custom nodes one by one, it seems that the node {ComfyUI_ezXY} was doing something wrong, so I deleted it and the error disappeared.

how did you figure that out?

[w1124c]

I found the root of the error, the custom node, by removing all custom node from the custom node folder one by one and inserting the custom node while launching ComfyUI each time.

[JonnyJV]

I found the root of the error, the custom node, by removing all custom node from the custom node folder one by one and inserting the custom node while launching ComfyUI each time.

Only problem is.. some of us have about 10,000 custom nodes installed.

[ltdrdata]

I found the root of the error, the custom node, by removing all custom node from the custom node folder one by one and inserting the custom node while launching ComfyUI each time.

Only problem is.. some of us have about 10,000 custom nodes installed.

The method developers use to find such issues is called binary search or halving. Using this method, even with 10,000 custom nodese, you can find the cause with just a few tests.

First, remove half of the installed custom nodes and test. If the problem persists, remove half of the remaining nodes and continue this process. If the problem doesn't reproduce, swap the remaining nodes with the ones you removed, then remove half of these and test again.

[BlairBrooksBB]

Hi. I was having the same problem, and after exploring the custom nodes one by one, it seems that the node {ComfyUI_ezXY} was doing something wrong, so I deleted it and the error disappeared.

This did the trick getting rid of that folder or node, fixed that situation for me.