I don't like the current 500. That's sharing the same conceptual space as
NPE, bugs and other hard failures for which IT should be paged at 2:30 am.
5xx indicates that there is a problem with the server and that there is
nothing the client can do, and also would typically be flagged by
monitoring
: I still think 503 is appropriate when timeAllowed is exceeded. The
: service requested is a reponse within the set time. That service is not
: available. Here are the RFC definitions of 500 and 503. Exceeding
: timeAllowed isn’t an “unexpected condition”, it is part of the normal
: operation
