Elasticsearch failed

I'm repeatedly getting this error over the last 3 days for a routine search that has always worked until now. Is there an issue here that is being fixed?

Hi, I spoke with one of the iRecord developers and he said: 'It’s just a generic error caused by any response from the code which handles Elasticsearch returning a response that is not OK. Reasons I’m aware of include timeouts (when server performance is poor due to load or slow code), or sometimes a search string with a special character (e.g. search for just a single “ character).'

He also mentioned they are constantly improving the system to reduce these types of warnings in iRecord. 

Thing is, if I go into "Explore all records" and create a filter with say "What = Sorbus", selecting "Sorbus" from the drop-down menu it comes back instantly with two MessageBoxes saying  "Elasticsearch query failed". This happens on two different computers, with Bing and with Google. And I have been making such searches routinely for years, always successful until 3 days ago. My connection is "fast" according to the Which SpeedTest. Now, today, if I try to load a record it comes back with "Data could not be saved - Validation errors occurred ... An error occurred whilst validating the information ...More information ... in warehouse logs (2025-07-25 15.51.55) ... more information related to occurrence general ... [and] ...sample general ..."

I am suggesting maybe there is an issue somewhere. If it is at my end how do I make contact to get help solving it?

I have the same issue, for the past few days whenever I try to search my records I get the Elasticsearch query failed box popup. I've emailed a screenshot.

I am also getting the same pop-up error message "Elasticsearch query failed" on 'Explore All Records' when I try to filter by e.g. species, taxon group or vice county. I think it started at the end of last week, and it's the same today.

Hi Oli, I've been having the same issue for several days now. The Elasticsearch failure message pops up after inputting the first piece of data into the Explore All Records search.

Same problem for me, first noticed Friday 25th. If I create a search filter the Elasticsearch query failed message immediately pops up twice, and then at every subsequent move of the map to a new search location.  All new filters are so afflicted. 

I can add one additional characterisation. A named stored filter I created some months ago works as normal when applied. However, creating a new filter, storing it and applying that is not a workaround - the new stored filter suffers with the same problem.  To summarise: existing stored search filter still works, any and all new search filters, stored or transient,  fail.

The problem was fixed but if you are still getting this error message, please share with us the problem here. Best wishes.