Catch Errors(Var Ports) node error message

[mychoi]

Hello,
I’m reaching out to understand the meaning of the error encountered in the Catch Errors node.
The following error occurred:

“encountered scope-end without compatible head!”

The workflow was executing properly up to the Catch Errors node.
Afterward, without making any changes to the workflow, I re-ran it, and it executed successfully.

However, I’m unsure under what circumstances this error occurs and how to respond if it happens again.

The workflow in question is used by our client, making it difficult to share or replicate.
We appreciate your understanding regarding our inability to provide the workflow for review.

If anyone has encountered or resolved this error, I’d appreciate your advice.

Thank you.

[MartinDDDD]

Hey there,

can you at least create a minimal example that reflects the structure of the workflow?

I think I have seen something like that when a branch ended in catch node without originating from a try node… but this is just a vague best guess w/o additional information…

[mlauber71]

@mychoi you might want to check the ‘wiring’ of the try/catch construct. Sometimes if does help to enclose the operation in a Component or Metanode

Understanding Problem Error Handling Loop

@robbsen OK I think I built something you might be able to work with. The important points are: encapsulate your loop in a component. Otherwise KNIME seems to have a problem to identify the Try-Catch block provide an empty table with the same structure as the one you want to collect at the end of a loop. I think you also could just use one table with one column and allow changing data structures in your Loop-End (you might have to clean that up later) I have not fully worked out the use of the…