Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detail pages fails too quickly #940

Open
MortenHofft opened this issue Feb 10, 2025 · 0 comments
Open

detail pages fails too quickly #940

MortenHofft opened this issue Feb 10, 2025 · 0 comments
Labels
GBIF.org parity Required to replace GBIF.org

Comments

@MortenHofft
Copy link
Member

MortenHofft commented Feb 10, 2025

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.

@MortenHofft MortenHofft added the GBIF.org parity Required to replace GBIF.org label Feb 10, 2025
@MortenHofft MortenHofft changed the title dataset page fails too quickly detail pages fails too quickly Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GBIF.org parity Required to replace GBIF.org
Projects
None yet
Development

No branches or pull requests

1 participant