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+OR+rail+OR+dillo+OR+transit+OR+train+OR+streetcar%29+%28austin+OR+atx%29%29&rpp=100

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

Reply via email to