When a login page just says something went wrong, I have no idea whether the service is down or there is something I can fix. Why can't software give a more useful explanation without dumping technical details on the screen?
Why do so many apps give such vague error messages?
Answers
Security is one reason, especially for financial services. Detailed errors can reveal internal system state or other information that someone could use to probe the service. The technical details can instead go into server logs for support or developers.
That doesn't mean the user has to get no guidance at all. A message can say that the service couldn't complete the request, suggest a next step when there is one, and leave out sensitive implementation details.
Reply to this answer
Sometimes the page genuinely doesn't know much. The browser might get a server error response without a useful explanation, or a request might fail without clearly identifying whether the connection, browser, or service was responsible.
The backend can be designed to return safe error categories, but that takes work. If the cause is uncertain, the message should say so rather than confidently blaming the user or claiming the service is down.
8s~cobblewhisk_731:
That uncertainty would still be useful to know. It beats guessing whether changing browser settings will help.
Reply to this answer
There's also the boring answer: one catchall message is cheaper to build than a set of specific, tested messages. Teams have to decide how much time to spend on error handling versus other work. That can leave users with a pretty frustrating experience, even when security isn't the main issue.
Reply to this answer
The useful distinction is whether the person can do anything about it. If a field needs correcting, say which field and why. If the service knows it has failed, say the problem is on the service side and that the user may need to wait.
And if a browser extension might be interfering with a payment popup, a troubleshooting suggestion could help without pretending the extension is definitely the cause. An error code for support can be useful too, provided it doesn't expose sensitive details.
r.615~torlavo:
Even being told there's nothing to fix locally would save people from wasting time on settings that aren't the problem.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_v64!plorvani.3:
That still depends on the error being logged and monitored. A generic message on its own doesn't guarantee anyone knows there's a problem.