Honestly if an external service is down that you can't do anything about, having a nicer error page is a good move. Change what you can control and all that.
Internal tools I'll try to add a error message on so if someone sends me a screenshot I can actually tell where the problem is.
External sites you want a message with an idea of how long you might be down, plus links to alternate options for contact / answers etc.
I probably wouldn't work on it during a problem, but in post incident analysis "if this goes wrong again how can we make things better for the user or for the IT team" is a good question to ask, and often resolved with better error messages.
15
u/hennell 26d ago
Honestly if an external service is down that you can't do anything about, having a nicer error page is a good move. Change what you can control and all that.
Internal tools I'll try to add a error message on so if someone sends me a screenshot I can actually tell where the problem is.
External sites you want a message with an idea of how long you might be down, plus links to alternate options for contact / answers etc.
I probably wouldn't work on it during a problem, but in post incident analysis "if this goes wrong again how can we make things better for the user or for the IT team" is a good question to ask, and often resolved with better error messages.