Hello, We get frequent and seemingly-random HTTP 500 errors when calling the search API. Sometimes it's 500, sometimes 502. It's definitely not throttling, as we don't make that many calls and I know from reading here that those errors have a specific message.
I've tried without success to find particular searches, times of day, etc. that are more or less likely to fail. Eventually I wrote a little program that generates random three-letter nonsense words and calls the search API with wget for each one. Out of 100 different search terms, usually there are 3-10 failures. If I try the same search terms again, sometimes the ones that failed will now work, and vice versa. This behavior is similar to what we see in our production code, which is completely different but also fails randomly and fairly frequently. Any ideas? We'd love to get a solution, since even with retry policies the errors are frequent enough to really hinder our ability to get search results. On a related note, is there any news on availability of the content firehose? Last I remember reading, it was going to be made available to "trusted partners" at the end of January or beginning of February. Our ideal solution would be to have access to the firehose so we can index and search the content on our side. Thanks!
