I am also facing the same issue, https://twitter.com/vsr/status/10199624984
On Mar 10, 3:09 am, Brendan <brender...@gmail.com> wrote: > I've noticed that when trying to get the entire status timeline for > some users (user ID 49777412 was one such user), requesting a page > (say the first page) of 200 tweets results in a 502 error. Retrying > the request a several seconds (5 seconds, in my case) later succeeds. > When requesting the second page of statuses, it again fails, but a few > seconds later it succeeds. > > It seems as though there's some caching issue happening in which the > initial request will take too long to return so Twitter returns a 502 > error, and by the time the second request happens the data has been > retrieved and is ready to serve the request. How should I go about > avoiding or reducing the occurrence of these errors? > > Thanks, > Brendan
