My resume: Classical understanding of an error of unclear or interpretable origin: end product is failing -> it's a failure in the end product -> maker of the end product is (at least more) responsible for the failure (than the end user). I'm understanding your interpretation as: our team is making no failure -> our product is o.k., even when it's failing. Times are changing. If I had got such an error message a fifty years ago belonging to the software product I was responsible, I would have had to prove without doubt, that another developer is responsible for this error, and then send an error message to him. The greatest error I could have made would have been to send back an error message for the failing product of my employer back to an instance outside.