@atpfm the “write good error messages” resonates. We have a system at work that talks to ours (let’s call it ABC) *a lot*. They have error messages that say “Failed to connect to ABC.” so we get sent them with “please explain what’s wrong at your end.”

What the error message SHOULD say is “Failed to call an API which connects to another component which requests yet another component to use a connection pool to actually talk to ABC.”

Guess where 95% of the problems lie.