Hi @BenjaminMoser, good though Node monitor is, the logfile allows me to see things that I cannot get from it.
For example, I can log messages using java snippet/java edit variable. I can also see when an unexpected error occurs (sadly KNIME 5.4 has had some glitches with table viewing, and it’s been useful to see when these have occurred)
… yes I work almost entirely in Modern UI these days. There are only a small number of reasons now that I switch back to classic.
One is to be able to Ctrl+F to find a node.
On a large workflow, it can be difficult to remember where a particular node is and search for a node’s annotation is a must before I can fully endorse MUI.
The second aspect of MUI which for me continues to fall a little short is table viewing performance. If processing in a loop, for example, the modern table viewers (and the bottom data panel) cannot keep up with the display of data; by the time they’ve got to the point of loading the data, the loop has moved on to the next iteration and so they continually show a “nothing to display” message, whereas the classic-style tables can populate far more quickly and so you get a brief display of current data.
Consequently I sometimes return to Classic for execution of a workflow, but more commonly I now drop Interactive Table (Legacy) viewers to provide that kind of “warm feeling” of progress (i.e. seeing the data flashing by 
)
Mostly I’m dissuaded from the switch back to CUI because I often have several workflows open at the same time and having to close them all is inconvenient.