sometimes, it's follows a clear pattern. request 100, fail. request same 100, success. repeat. --- that's likely because they load it in the cache once they hav

sometimes, it's follows a clear pattern. request 100, fail. request same 100, success. repeat. --- that's likely because they load it in the cache once they have the results. it halves my success rate, basically. but sometimes it's just random (depending on twitter overall traffic I'd assume). plus, some records are faulty and can not be fetched. so this causes other issues as well and drops the api call.