Our team seems to have found the solution. The error orignated in the proxyEndPoint and the default fault rule should be located here to catch the error. When inside the targetEndPoint flow the rule gets skipped. We caught it by putting a raisefault ...