Oauth/token offers an unexpected 500

With no changes to our software, the POST oauth/token endpoint that used to accept a refresh token to get a new access token is returning a 500. The error (below) is not helpful, since it is looking for a property we don’t need or provide on an undefined object.

Hey @cubap. The most likely explanation here is a rule throwing this unhandled error.
For example, code that tries to access context.request.query.redirect_uri in a refresh token exchange where there is no query.

Can you check that?