Closed sqlninja closed 1 year ago
I think may have been something going on with Twitter, as messages are going through again, so disregarding for now...
Turns out to be a similar issue as #934 I have added more commentary on that issue
I'm poking this issue because it appears that the empty response could be related to a rate limit (we saw that we were limited via the web app), but the responses coming back from the gem were just empty, thus not throwing the TooManyRequests error.
So got feedback from Twitter about the empty response coming back:
@StackedSports - It sounds like you’re hitting the DM limit, either the: Technical limit: https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event Or the daily limit: https://help.twitter.com/en/rules-and-policies/twitter-limits Whichever comes first.
Which leads to me why isn't the TooManyRequests error being thrown by the gem?
In the last few days I am no longer able to send DMs. Just getting this error:
This line is breaking now because the response is empty
I know definitively this was working on 2018-07-20, because I was able to database the DM id from previous sends...