Public endpoints refresh failing

[bpasquer]

Creating issue from email by Toni(2024-04-10) for reference:

Some recent database corrections are not being reflected on the public endpoints that Reef Species of the World, FIshbase, Atlas of living Aus, etc use. Some of these changes were made months ago so I would expect them to be reflected in the views used by these websites. Some examples are: I changed all records of Trygonoptera mucosa in Victoria to T. imitata, and added observations of Pictilabrus brauni to a survey in Albany. The T. mucosa observations have not updated on distribution maps on these websites, and P. brauni doesn't have a page generated for it on Reef Species of the World

I can confirm:
•             Pictilabrus brauni is not appearing in the species_list layer (the layer that these external sites use to generate species pages), but the species has been entered and has observations attached. I can confirm a correction was made at the end of last year and this species was added to survey 6002097 in Albany, WA, however the species is not present in the species_list layer (mapped_id = '6002097'). I can see the observation for this species in the ep_m1 layer.
•             Checking the species page for Trygonoptera mucosa (mapped_id 1837), they are still including records from Victoria (after all records from Victoria were corrected), so again, I’m not sure what is happening here (see <a href="(https://reeflifesurvey.com/species/trygonoptera-mucosa/) This species is often smaller, but appears practically identical to T. imitata - and is best distinguished based on location (this species only found in South Australia and Western Australia). It differs from T. testacea in lacking the small dorsal fin on the tail. Most commonly seen in shallow sheltered bays near seagrass beds.reeflifesurvey.com

I can confirm that the only records for this species are showing in the end points (ep_m1, ep_m2_cryptic_fishes) are from Western Australia as expected so I’m not sure why points in Victoria are still appearing?

Response from Bene 2024-04-20:

We sincerely apologize for any inconvenience caused.
We have corrected the issue preventing the latest correction updates from being reflected in the public endpoints.
The problem happened because of an harvester issue in relation to the publication of a new endpoint for TPAC (#1286)
The endpoints have been refreshed overnight successfully.