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
Experiencing significant delays in loading the alert.riparias.be webpage, with load times from over a minute. Additionally encountering Forbidden (403) errors when attempting to access the site (after login screen). The following issues have been identified:
Loading Time Delay: Users across multiple devices (three separate laptops) and browsers (Edge and Chrome) have reported excessive loading times. Even after clearing the Chrome cache, the issue persists.
Forbidden (403) Errors: I have encountered Forbidden errors, both in regular browsing mode (Edge & Chrome) and incognito mode (Chrome)
No Improvement with Different Accounts: Switching to alternative accounts does not alleviate the loading time delay or resolve the Forbidden errors
Slow Initial Popup: In some instances, the initial popup, particularly the species selection, loads extremely slowly, resulting in delayed display of labels and species names lost.
Long Page Load Times: Various pages within the website, including the front page login and area selection, take several minutes to load
On some occasions pages do load, but this seems unrelated to size of request (# polygons/species)
fi. loading the parcels from DVW costs 3 minutes, and loading the tiles costs another minute, for a total of 180 observations
The text was updated successfully, but these errors were encountered:
This is due to the fact that GBIF alert (the tool behind the site) doesn't currently deal very well with the large amount of data (users / alerts / observations) in the system. We plan to structurally fix that, but we might have to circumvent the issue first (by importing only recent data from GBIF first) because I might not have the availability to fix it immediately.
Experiencing significant delays in loading the alert.riparias.be webpage, with load times from over a minute. Additionally encountering Forbidden (403) errors when attempting to access the site (after login screen). The following issues have been identified:
The text was updated successfully, but these errors were encountered: