Avoid the exception supression that is hapenning on the YAML processor invocation
While on a call with a customer we've found this code on the YAML processor invocation which was hiding the underlying problem. We should handle the error differently. The underlying error at least gets logged.