Oh no, actually it worked partially! The rich logging handler stops logging when I do this change, but the rich backtrace (when something breaks) is still there. This can be tested when you call a pipeline that has wrong inputs or a pipeline that does not exist, for example. So this is only for the console logging, not for the actual backtrace when an exception occurs