Fortunately, clicking somewhere in the workbench and then clicking again on the Expression node revives the node, but I can no longer save changes. Same with the Expression Row Filter, so I guess even more nodes could be affected. I see this both in the configuration panel at the side, as well in the expanded version.
Is this a general bug, or is something wrong with my installation? I’m using KAP 5.5 on Windows.
Probably related knime log entry:
2025-09-04 12:36:25,543 : WARN : Thread-119599 : : KnimeBrowserView : : : An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing. (source: ``https://org.knime.core.ui.dialog/uiext-dialog/org.knime.base.expressions.node.row.filter.ExpressionRowFilterNodeFactory/row-filter.html``; line: 0)
Been battling this one a ton as well. Glad to see you are on it! Thanks!
I also find that when opening the node, it tends to only show the expression builder area without the column name references or clickable searchable expressions. I then have to minimize the window and the maximize it again out of the UI config window to see the full config window.
I found a ticket mentioning this (internal reference NXT-3298). Apparently the incomplete loading happens, if you open the large mode before the small mode has finished loading. Would you mind double checking, if that’s also the case for you? I.e., waiting until the side panel loaded completely before opening the large dialog works well.
That seems to be the issue. Muscle memory causes me to quickly double click nodes. The issue was not present if I was mindful and waited a few seconds. I turned off the embedded config windows to get around the issue.
I have the same warning message in the log file. For me, it happens when I check the “enable reporting” box in the layout editor of a component. After that, it is no longer possible to execute the nodes.
I am not sure, I understand you correctly. To clarify, after you created a component, you opened the Layout Editor and enabled report generation.
Did you then go out of the component and connect a Report Template Generator node to the new Report input of the component, which was added as a result of enabling the report generation? Like so:
