Indeed, the response is a failwhale, which in my loop creates a return
of 0 tweets, and than abandons the loop. Like you said I can put in
one or two retries before breaking the loop. It is still funny though
that the error happens everytime further down the loop, and stops
happening once all
I've seen this happen quite regularly when you have count of 200 and
either rts or entities enabled. I submitted a bug report and was
simply told to lower my count because the system often takes too long
to process rts and entities the first time they are requested.
On Apr 11, 8:35 am, Randomness
