Cannot access Royal Ontario Museum.

[entogeek]

Thank you for reporting this issue. Please describe what happened.

Cannot access Royal Ontario Museum.

Error message for diagnostics

Mw@https://react-components.gbif.org/lib/gbif-react-components.js?v=c486aa8cdc3578b030b7a9d57318120d:68:519350
Le@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:100:3
Re@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:113:271
Pj@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:233:55
di@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:168:307
Nj@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:168:238
sc@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:168:96
gf@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:162:109
$g/<@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:73:230
unstable_runWithPriority@https://unpkg.com/react@17.0.1/umd/react.production.min.js:24:26
Za@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:73:8
$g@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:73:178
ja@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:73:111
Pa@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:157:212
Me@https://unpkg.com/react-dom@17.0.1/umd/react-dom.production.min.js:110:252
gbifReactComponents</q/S/<@https://react-components.gbif.org/lib/gbif-react-components.js?v=c486aa8cdc3578b030b7a9d57318120d:16:35311

Location: https://scientific-collections.gbif.org/institution/9384011e-4d9b-4488-a5dd-5cb67a3c17f7

[MortenHofft]

Thank you. Not exactly an informative error message that I have provided myself with in this case.
And I cannot replicate it either.
I will investigate, but it probably isn't something I can easily spot. Better error messages could be a beginning.

My guess is a temporary API/backend outage/degradation, but it would be nice if those were handled more gracefully/informative in the UI.