You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we modified query tool to handle partial node failure/success it seems we forgot to take node API into account so part of the code looks for custom fields in the response object e.g., response.data.errors that are specific to the response coming from the federation API.
This results in the parsing of the options failing when the query tool points to a node API i.e., NB_IS_FEDERATION_API=false. So the requests go through and come back green but you will see no options in diagnosis and assessment tool dropdowns.
The text was updated successfully, but these errors were encountered:
When we modified query tool to handle partial node failure/success it seems we forgot to take node API into account so part of the code looks for custom fields in the response object e.g.,
response.data.errors
that are specific to the response coming from the federation API.This results in the parsing of the options failing when the query tool points to a node API i.e.,
NB_IS_FEDERATION_API=false
. So the requests go through and come back green but you will see no options in diagnosis and assessment tool dropdowns.The text was updated successfully, but these errors were encountered: