In order to use Twitter API v2 we have configured a project and added our production/staging/test applications into it.
Now we can’t create concurrent batch compliance jobs using bearer tokens from different applications - such attempts result in 409 http response.
It’s mentioned here that we can have one concurrent job per job type at any time, but it turns out to be one concurrent job per job type and per project even though a bearer token is acquired per application.
Is this expected behavior?
There is no notes about Compliance API being throttled on a project level and no 409 error description in documentation Introduction | Docs | Twitter Developer Platform
3 Likes
