Sometimes the POST /2/tweets endpoint returns errors with the following response, even though the tweets are actually published
{"title":"Service Unavailable","detail":"Service Unavailable","type":"about:blank","status":503}
After troubleshooting the issue, we narrowed down (at least some of the errors) to having video files 3840x2160 (I can provide a sample if needed)
It is worth noting that the endpoint “POST /1.1/statuses/update” doesn’t return any errors (it also succeeds in posting the tweet)
4 Likes
kush
#2
We are getting the same error on the same endpoint i.e. POST /2/tweets.
And I can confirm in our case, that it does not depend on the fact whether a tweet has a video or not.
It is pretty frequent and our users’ experience is getting affected because of this.
Any help on this would be appreciated.
We’re using the node-twitter-api-v2 library to make calls.
2 Likes
Update on this, the problem is still happening, perhaps more frequently than in the past. It appears to be not only related to videos, we have seen this error as well on tweets without videos
It can be reproduced consistently using the same inputs, and from multiple accounts
And it can be reproduced going directly against the restful API, even without a library
And again, trying the same inputs with v1.1 returns successful results
1 Like
OK some progress in narrowing things down
If this image was uploaded it gives 503
However if this one was uploaded, it gives 200
Notice same dimensions, just different pixel data
I think we need some help from the twitter API 2 dev team here, please!
2 Likes
We are still experiencing this issue one month later
1 Like
I can confirm that we’re having the same issue for a lot of our users.
The issue seems to be almost exclusively happening on video upload for us.
Would be great to get the Twitter v2 team looped in here!
Kind regards,
Simon from FeedHive
1 Like
tjlull
#7
Thank you all for the diligence reporting and providing updates here, and thanks for your patience. Despite the consistency some of you are seeing, we’re having a hard time reproducing. Please share any additional patterns you’re noticing. We’re continuing to look into this; stay tuned.
Hey Travis,
If you check out the images I provided, you can reproduce the problem 100% of the time (I just confirmed that I can still reproduce it with the exact same image)
There are other cases of videos, but I am not sure why it happens, I presume if the image one is fixed, videos will too
Thanks
Samir
1 Like
We are experiencing this consistently as well and ended up reverting back to V1. Eagerly awaiting a solution.
We’re experiencing the same issue, mainly with video uploads larger than 40mb, and carousels of 4 images. Seems like something’s timing out on Twitter’s side.
The same carousel of 4 images posted twice:
Info from our Lambda (running /2/tweets) below when posting a video:
Start time:
3 Nov 2022, 03:08:19.720 UTC
End time:
3 Nov 2022, 03:09:19.422 UTC
Error:
{
"title":"Service Unavailable",
"detail":"Service Unavailable",
"type":"about:blank",
"status":503
}
Cheers,
Aivaras from www.ocoya.com
Hi guys,
Maybe it’s related to this topic.
In the cases I have encountered, 503 error is returned with subtitled videos. However, the subtitled videos are tweeted to timeline despite the error.
It sounds related, though it is not subtitles, it’s the media format.
If you look above, you can see I provided two png files, one that causes 503 the other does not.
It happens with videos too, but I think it’s a lot easier to troubleshoot png than video
2 Likes
