If a user enter a meta data that doesn't exist in kb the Api responds with 500
If a user enters metadata that doesn't exist in kb the API responds with 500 internal server error and a very generic error message that may occur in any case if the API has accessibility issue.
It should return an appropriate response code other than 500. As its not an internal server error I believe its something like 404 or even 200 with no match found in kb something like that.
You guys should handle this exception.