Yes, due to lots of recent growth we're bumping up against some capacity limits and working on them right now.
In the mean time, some very complex queries will time out. I'd encourage you to back off on your rates, and please to not aggressively retry the complex queries that fail [we don't cache the failures, but will probably begin doing so in order to prevent people from pounding the system with retries while it is already straining] thanks On Apr 28, 11:08 am, rcauvin <ro...@cauvin.org> wrote: > It happens now just about every time when I'm trying to get the second > page of results for a complex query. For example, this one is failing > at the moment: > > http://search.twitter.com/search.atom?max_id=13019381815&page=2&q=sna... > > The first page of results comes through fine. And if I make the query > less complex, the results come through fine as well. > > On Apr 27, 10:42 pm, rcauvin <ro...@cauvin.org> wrote: > > > > > My program that uses the search API has over the past couple of days > > been getting a lot of 502errors. > > > On Apr 26, 5:15 pm, mikawhite <mikawh...@me.com> wrote: > > > > Unit = an 'internal tweet' for each null/502/503 result from the > > > Search API. > > > > -- > > > Subscription > > > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
