Nondeterminstic behavior for lists/members/create_all

[ducu]

Hey did it recover for you? I got stuck as well can’t even add to lists manually…

[gregorygunner]

Hey there guys, I’m getting pretty much the same thing. Yet majority of the time I get 0 members being added, even though the call is the same, and my screen_names are not protected.

In my first attempt , I got 497 people added, out of 499. Then I tried a larger list which only got 147 out of 1000. Following this I got an error back of “Over Capacity”. Subsequent calls I’m lucky to get 1 name added to my lists.

@andypiper any further ideas yet?

[computerpoetry]

At this point I’m just creating a new list at most once a day. It’s not ideal at all, but sufficient for my project.

[andypiper]

Unfortunately I’ve been deep in prep for @Flight so haven’t had a chance to dig deeper. Bear with me.

[gregorygunner]

Appreciate the effort Andy!

[ducu]

They say you have to add 100 at a time
https://dev.twitter.com/rest/reference/post/lists/members/create_all

I’m doing that and sleeping 100 seconds between subsequent calls but it still gets stuck after few times. Hoping @andypiper gets back to us, cheers.

[ryanwi]

I first noticed this behavior around the beginning of July along with others that work with lists extensively. At the time, I assumed it to be a new, secret rate-limit (or at least was not updated in the docs, I know docs can trail behind). But, glad to see this thread since it is still happening and the docs have not been updated, if indeed it is a rate limit of sorts.

I can confirm that the call behaves differently with a identical set of user IDs, which was why I assumed it was some type of limiting.

I can also confirm that once it starts happening (not all users added in the create_all) then attempts in the native Twitter Apps/site to add a member to a list also fail, again pointing to some limit on the user in the number of memberships that can be created in a given period. The error message in the Twitter web site is “Your account may not be allowed to perform this action. Please refresh the page and try again.”

[hiyounes]

I’ve ran in the exact same problem.

Can’t figure the origin: not related to ids, number of calls, existing list or not, and no error code.
It just worked fine 2 months ago (well, not after creating several listsx). Now, it just add very few people (sometimes 0, sometimes ~ 20). So I need to to make the call dozen of times to add up to 3k members.

Other issues related:

Creating twitter list results in additional list with 0 members

In our application we export people to twitter lists. When we export the list sometimes the api creates another list with zero people in it. I was wondering if other people had experienced this. It could possibly be a combination of https://twittercommunity.com/t/twitterapi-lists-members-create-all-with-100-user-ids-returns-http-status-502/10565 and https://twittercommunity.com/t/post-lists-members-create-can-t-create-mebers-in-list/7986

Lists/members/create_all not adding people to a list

Hi. We have recently noticed that our calls to the lists/members/create_all passing several comma separated list is ignoring most of the user ids passed to the endpoint. We have seen this behaviour both in our app (using the api) and in the apigee console. Here's an example: user_id: 2890020569,1456394982,2873784815,2625116151,2864623095,2879864339,1874923808,2828739661,520675155,2483032419,2901081005,1514316733,582707933 list_id: 189509955 slug: posttest This test list has already onl…

[ryanwi]

@andypiper Have you had a chance to dig into this? Let me know if you need more sample requests/description.

[jasonbaumgartne]

Has anyone found a fix for this or a workaround? I’m unable to use create_all to add accounts. As others have said, there appears to be some type of limiting on Twitter’s end or just an outright bug. Sometimes 1 account out of my list will get added, sometimes 0, etc. It is very erratic.

I may just use the create endpoint to see if that works better, but adding the 1,000 max for a list would be a lot of unnecessary API calls.

Also, I’m getting a 200 response back from the API even though none of the ids in my list are ever added. It’s very strange.

[eliasisrael]

I’m getting this same behavior using the REST API. In addition, attempts to add any users to a list on the account I use for testing also result in the “your account may not be allowed to do this” error mentioned above.

Please? Is there a rate limit or limitation to be aware of so that we’re not triggering this result?

We’re limiting our calls to this API to once each 10 minutes, and a max of 100 users added to the list each time. Should be well below the API limits as published.

[tsanch3z]

I’m experiencing the same behavior here:

• 200 ‘OK’ response from the API but members frequently not added
• No rates limit appear to change after I call the create_all endpoint
• As soon as I notice an issue, any attempt to add a user to a list through the twitter website result in the “your account may not be allowed to do this” message to pop

Am I missing something about this particular endpoint ? is there a limit on the number of users one can add to lists for a given amount of time ?

[parakweets]

We’re experiencing the exact same thing, for what it’s worth

[computerpoetry]

Can someone from Twitter put the time to at least confirm the existence of this bug? It’s been almost half a year and a lot of people are reproducing this issue.

[ameensol]

6 months later, same problem.

@andypiper please deliver us from this hell.

[electoral]

Any updates @andypiper? It seems to be getting worse, and by that I mean more restrictive in how frequently members can be added. This double secret probation is frustrating for many folks I’m sure. Why not publish what the limits are? (assuming it’s a secret rate limit, because after a year, I can think of no other reason for this to continue).

[ssolbak]

We’ve also ran into this problem as well. Even the curl command from the generate signature widget on https://dev.twitter.com/rest/reference/post/lists/members/create_all often adds no users to the list. This will happen repeatedly and often takes over an hour of retries (working well within the rate limits) gradually filling up the list with the twitter users we want in it.

In our case, the api returns no errors, it simply just doesnt add the users to the list.

[raghavio]

This is still happening. Can anyone from official team confirm? Please? @andypiper

[andypiper]

I’m unable to confirm any issues with this endpoint beyond the sporadic reports on this thread over an 18 month period. If you are able to share any further details then we may be able to investigate.

[ryanwi]

There were examples provided over a year ago. If we provide you samples will you respond?