Yes, it does appear the issue is fixed. Getting the second page of
results for a complex query is now working for me.
Roger
On Apr 30, 2:08 pm, mikawhite wrote:
> This issue is resolved this morning, 20100430. Thanks @evan & @ej?
>
> chart updated...http://tweetprobe.tumblr.com/post/551639110
This issue is resolved this morning, 20100430. Thanks @evan & @ej?
chart updated... http://tweetprobe.tumblr.com/post/551639110
Updated chart - hth - http://tweetprobe.tumblr.com/post/551639110
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
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=snappatx+OR+%22capital+metro%22+OR+%22cap+metro%22+OR+capmetro+OR+%28%28bus
My program that uses the search API has over the past couple of days
been getting a lot of 502 errors.
On Apr 26, 5:15 pm, mikawhite wrote:
> Unit = an 'internal tweet' for each null/502/503 result from the
> Search API.
>
> --
> Subscription
> settings:http://groups.google.com/group/twitter-dev
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
