Post

If you use the string “try again later” in an error message you should go straight to jail. It should be a standard rule in all linters.

I'd be curious to know what your standard solution has been to handle that scenario; everybody seems to have a slightly different approach. My general approach is to give them a message saying that an unknown error occurred and a link in the notif to an incident page, pre-filled with details.

I’m being a little bit facetious but you _always_ know something. If this is because you made some API call and got a 503 or whatever you know that you can’t currently talk to the backend and you should hopefully be able to link the user to more information (status page, support email, etc)

If you don’t have a status page, or you don’t have any way to communicate with your users when you have an outage, that’s a separate problem you need to fix.

0 reposts0 likes

I agree with that. Let me ask you though, if my app is up and the issue is say one endpoint in an API and not the entire integration, how would I meaningfully report expectations and resolution to the end user?

I don’t see how that changes anything. You would have a separate status page that reports that that endpoint is having problems. The error message can direct users to the status page. From there it’s the same playbook as before.

Sorry, realised this wording is weird. I’m not saying a status page just for this endpoint, I mean the status page should be separate to the rest of your infra so that it too goes down in tandem with your other services. Your status page can then be as granular as is appropriate for your app.