My assumption is that while the user may get this generic error, an error with actual detail goes to an internal team to actually look at what happened and fix

My assumption is that while the user may get this generic error, an error with actual detail goes to an internal team to actually look at what happened and fix it, with more detail. I recently worked on an internal app at work, and the UI team didn't want us to provide technical details in the error messages from the backend, because they didn't think it was a good experience for a user to get too much technical jargon. They wanted the conversation to die there. I had to fight to create meaningful error messages that would go to a support team, while they still kept sending something akin to "something went wrong" to the users.