2:56 pm


Gold
July 15, 2011

I'm wondering if anyone else is experiencing issues with ThingTweet in the last week or so. Many or maybe most posts are not making it to Twitter even though I get an HTTP/1.1 200 OK status back from the server. Everything looks fine on my end. It's a mature application that's been running for years and no changes have been made recently.
3:21 pm


Gold
July 15, 2011

5:04 pm


MathWorks
May 1, 2016

Twitter has been changing their APIs and has implemented some sort of rate limits in the last 2 weeks. I've had success by un-linking and re-linking my Twitter account with ThingSpeak to get ThingTweet functioning properly again.
How often is your device using the ThingTweet API to tweet? Are there any correlations to be drawn by changing your rate of tweeting and observing its impact on reliability of Twitter?
5:08 pm


Gold
July 15, 2011

8:03 pm


Gold
July 15, 2011

12:55 am


Gold
July 15, 2011

Tried testing with Postman and curl. I get the success response (1) and 200 OK status, but no tweet on Twitter. Any other ideas?
curl --request POST \
--url http://api.thingspeak.com/apps/thingtweet/1/statuses/update \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'cache-control: no-cache' \
--data 'api_key=xxxxxxxxxxxxxxxx&status=hello%20world'
8:16 am


Moderators
March 7, 2017

I am able to reproduce this issue, even after linking and unlinking.
On the second try, when I logged out of thingspeak before re-linking, I was able to get the tweet to go through.
When you re-link you should have to re enter your twitter credentials. If you don't have to re-enter, perhaps try logging out and then re-logging in incognito mode (that worked for me.)
11:56 am


MathWorks
May 1, 2016

Looks like Twitter is changing things on their servers. Here are the steps required to get it working again:
1) Unlink your twitter account from ThingSpeak
2) Log out of twitter
3) Log back in to twitter
4) Re-link your ThingSpeak account with your twitter account
5) Test your ThingTweet app in POSTMAN
6) Update your devices to use the new ThingTweet API key
Can you confirm this?
3:42 pm

October 30, 2018

6:14 pm


Gold
July 15, 2011

Vinod said
Looks like Twitter is changing things on their servers. Here are the steps required to get it working again:
1) Unlink your twitter account from ThingSpeak
2) Log out of twitter
3) Log back in to twitter
4) Re-link your ThingSpeak account with your twitter account
5) Test your ThingTweet app in POSTMAN
6) Update your devices to use the new ThingTweet API keyCan you confirm this?
No change, did not work for me. Tweets still not getting through. Symptoms are the same. Server still returns success response (1) and HTTP 200 OK. Does not work from Postman, curl, or updated devices. I do think the problem is somewhat intermittent. Occasionally a tweet gets through, but most do not.
What can we try next?
7:10 pm


MathWorks
May 1, 2016

Hmm. That definitely worked for everyone we tried it with at MathWorks. So, I am not sure what went wrong. Unfortunately Twitter doesn't show information about the requests made by each app, and what response they issued to the request. That would have been nice to be able to debug if the request made it to twitter and if they rate limited it.
One option may be to also try this with a second (different) twitter account linked to your ThingSpeak account, to ensure this is not some rate limiting that is causing the tweets to not be posted.
Maybe we can set up a phone call where you do a screenshare and walk through this together? Can you please send me an email vcherian (at) mathworks (dot) com with some times you are available and I can set something up.
7:40 pm


Gold
July 15, 2011

Vinod said
Hmm. That definitely worked for everyone we tried it with at MathWorks. So, I am not sure what went wrong. Unfortunately Twitter doesn't show information about the requests made by each app, and what response they issued to the request. That would have been nice to be able to debug if the request made it to twitter and if they rate limited it.
Wow. very interesting. I tried it twice and no joy.
One option may be to also try this with a second (different) twitter account linked to your ThingSpeak account, to ensure this is not some rate limiting that is causing the tweets to not be posted.
I do have another account that I almost never post to. I tried the following with it. Again no joy.
1. Log out of Twitter (account that my devices post to).
2. Log in to Twitter (secondary account, this was unlinked previously).
3. Twitter > Profile and settings > Settings and privacy > Apps and Devices > Revoke access for ThingTweet.
4. Log out of Twitter.
5. Log in to Twitter (secondary account).
6. Confirm in Twitter that no apps are connected.
7. Re-link ThingSpeak to Twitter.
8. Confirm in Twitter that ThingSpeak is connected.
9. Test with curl, Postman. No tweet.
Maybe we can set up a phone call where you do a screenshare and walk through this together? Can you please send me an email vcherian (at) mathworks (dot) com with some times you are available and I can set something up.
Yes, thank you. I'll email you shortly.
2:52 am

October 30, 2018

3:00 pm


MathWorks
May 1, 2016

This turns out to be the root cause:
https://twittercommunity.com/t/new-post-endpoint-rate-limit-enforcement-begins-today/115355
This is why the situation appeared to work intermittently. Unfortunately, when it stopped working, users trying to debug the issue resulted in more Twitter requests that locked us out for more time.
We're working with Twitter to find a reasonable solution. Thank you folks for reporting this issue and your patience as we work on it.
7:37 pm


Gold
July 15, 2011

Vinod said
This turns out to be the root cause:https://twittercommunity.com/t/new-post-endpoint-rate-limit-enforcement-begins-today/115355
This is why the situation appeared to work intermittently. Unfortunately, when it stopped working, users trying to debug the issue resulted in more Twitter requests that locked us out for more time.
We're working with Twitter to find a reasonable solution. Thank you folks for reporting this issue and your patience as we work on it.
Vinod, it was good talking with you today and I'm glad that the root cause has been identified. I hope Twitter will make an accommodation for ThingTweet. While 300/3 hours is a reasonable rate limit for an individual user, that's not the reality of the situation with ThingTweet since multiple users funnel through it. There was a period of time this afternoon when I was seeing tweets get through, and it's working as I write this. So it all seems to fit together. Thanks again!
1:19 pm


Gold
July 15, 2011

Vinod said
Thanks for confirming, Jack.We have some confirmation that our developer account has been approved. We believe that this issue is resolved for now. Unless there is a surge of tweets from ThingTweet, we should be functional for all users.
My once-daily status message came through OK today at 13:00 as usual! I'm checking with a friend with a similar setup to see if his is working too.
5:40 pm


Gold
July 15, 2011

7:27 pm


MathWorks
May 1, 2016

JChristensen said
Vinod, does the developer account increase the rate to a higher level, or remove it entirely? In other words, if ThingSpeak traffic grows, might the same issue occur again?
It is possible. We'll put in some safeguards on ThingSpeak end to reduce the likelihood of this, but, we are ultimately dependent on Twitter API for posting Tweets.
Most Users Ever Online: 166
Currently Online:
35 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
rw950431: 272
Vinod: 240
piajola: 95
turgo: 70
vespapierre: 63
Adarsh_Murthy: 62
Member Stats:
Guest Posters: 1
Members: 8665
Moderators: 1
Admins: 2
Forum Stats:
Groups: 3
Forums: 14
Topics: 1600
Posts: 5760
Newest Members:
Advantagetreeexperts, laundrydaddyuk, techhhelp5, ken, tran, huldacormierModerators: cstapels: 460
Administrators: Hans: 405, lee: 457