Expand error catching for request to graph #303
Labels
maint:usability
General improvements to product usability that are unrelated to feature prioritization.
type:maintenance
Upkeeping efforts & catch-up corrective improvements that are not Features nor Bugs
(See related neurobagel/federation-api#74 for reference)
The type of request error we're currently trying to catch is too narrow:
api/app/api/crud.py
Lines 52 to 57 in 1f89c22
any other type of timeout or error from the graph is not caught and results in an
Internal server error
. We may want to add a catch for a generic Exception and return any error message we get so API users get a more useful error. Basically, we want to minimize the dreadedInternal server error
!!!!We may also want to double check the error catching for requests related to other API endpoints, such as
/attributes
.The text was updated successfully, but these errors were encountered: