then we want to show that error message to the user
Do we? Always? Even if there's not a thing that can be done about it? Even if the error message is in computerese? Whilst error messages are endlessly fascinating to us when we are debugging, I think we're inclined to forget that the user has absolutely no interest in all this esoterica and arcana. As a user, I don't give a damn about the terminal state of the oojamaflip whilst traversing the thingummy at the flobadob. All I want is the result I asked for and a simple yes or no to whether I got it with perhaps an indication of whether or not it's worth having another go. For the user being told there's an error is most of the time about as useful as those Danger Falling Rocks signs on roads. So what do you expect me to do about it?

A lot of applications it seems to me could benefit from an automatic retry or two rather than rushing to tell me completely useless details of an error. If it's something I can do something about like a mistyped value or a poorly chosen setting then say so but say so in English! Otherwise it's just way too much information!