Open maiamcc opened 6 years ago
Resolved in 37d3eb5ebd421adf06f066e2f370d39e96787e0a
Reopening because I had to revert this change in b8ae0603b5f022ef377964acf055c01f1778566f. I need to either figure out why we're getting apparently erroneous 401s for specific queries or make detection for invalid creds more intelligent (maybe detecting N consecutive 401s or something).
Tried to run
sync_tweets
with invalid creds and got a whole pageful of the same error:Ideally, should detect a bad credentials error and bail rather than trying (and failing) to get Tweets for every rep.