Any cool results you achieved from that?
I like the idea of being proactive instead of reactive when it comes to addressing some of our exceptions.
For example, I can look at the frequency in which different type of exceptions occur for any Action.
If I notice a particular method having a lot of exceptions I can dig into it further. It could be a number of things (failing BPM, bad data, user has no idea what they are doing, etc). Then we can approach ways at reducing the amount of exceptions our users encounter. It could be as easy as the user needs more training.
I want this too, but I imagine it could get quite difficult separating the signal from the noise. There is a reason doctors donāt do full body scans for preventative care.
For example, someone with fat fingers is going to generate a lot of āRecord not foundā errors across a variety of business objects in the logs. They correct the typo immediately and itās no harm no foul. On the other hand, a user who has no idea what theyāre doing botches the products and pricing on a sales order, but has no exceptions along the way so nothing is logged.
Sadly, that would also require that the user READ the message, INTERPRET its meaning, and ACT according to that interpretation. I wonāt say it will never happen, but I havenāt seen itā¦
Thatās because they didnāt have to call you. Sample bias.
hehehe⦠I was āthe IT guyā for 30 years before coming over to the dark side⦠I got the calls.
Yes you got the calls for the people who didnāt read. You never got the calls from the people who DID read it.
And all these awful errors only train people more and more to close them without looking, because they are always useless.
Nah, Iād say he got calls from bothā¦I know the feeling all too well.
Reading and comprehending what was read are two entirely different concepts.
Regardless, just because some people pay no attention to the fuel warning light on their car and drive it till it dies is no reason to get rid of it for the rest of us.
Like Al and his Dodge?
Seriously, the more info you can get into an error message the better. A cryptic correlation ID is not sufficient. I donāt expect users to translate what it meansā¦but I do expect them to forward me the exact details so it can be investigated further.
As they say in AA⦠āExpectations are preconceived resentmentsā. I would love this to happen but I certainly donāt expect it. The best error message in the world apparently becomes invisible the third time. I get calls like, āNormally I have to click OK on errors 3 times and this time it was 4, what should I do?ā
Letās not overlook how satisfying it is to ask the person who called to read you the error message, only to sheepishly discover the answer to their question. I donāt want to lose that.
No lies detected. I know itās expecting a lot, but if a user calls/emails for help then they need to give us clues to solve the problem. We arenāt mindreaders.
If you are on prem you can get useful error messages, just have to modify the web.config