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
The dataset page will show a 500 error even if it is just the occurrence query that fails.
It would be nice to just show what we can in those cases and notify the user about the partial page render
same goes for CollectionSummaryMetrics on collection detail page.
We should go through all pages where we throwAllErrors: true,
and revisit if that is really the best approach. In cases where it isn't essential data we should fail gracefully and inform the user about failing backend requests instead. Possibly retry a single time after a few seconds.
Ideally we have a general approach for how to decide when something is seconday vs essential.
And a general approach for how we notify users.
The text was updated successfully, but these errors were encountered:
The dataset page will show a 500 error even if it is just the occurrence query that fails.
It would be nice to just show what we can in those cases and notify the user about the partial page render
same goes for
CollectionSummaryMetrics
on collection detail page.We should go through all pages where we
throwAllErrors: true,
and revisit if that is really the best approach. In cases where it isn't essential data we should fail gracefully and inform the user about failing backend requests instead. Possibly retry a single time after a few seconds.
Ideally we have a general approach for how to decide when something is seconday vs essential.
And a general approach for how we notify users.
The text was updated successfully, but these errors were encountered: