Not sure what you mean with your last question? But thanks for your answer.
I can obviously use separate node-outputs for such notifications, but that's more work and more clutter. I like the functionality of the catch node... like magic
If the function encounters an error that should halt the current flow, it should return nothing. To trigger a Catch node on the same tab, the function should call node.error with the original message as a second argument: