You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later. #32120
Unanswered
AutomationUIUser
asked this question in
API and Webhooks
Replies: 2 comments 2 replies
-
|
@AutomationUIUser there are dfferent types of rate limits, see #rate-limiting. |
Beta Was this translation helpful? Give feedback.
2 replies
This comment has been minimized.
This comment has been minimized.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When trying to create multiple issues from API, creation gets blocked after some operations. Getting below error when trying to process the API.
"message":"You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later."
At this time API header response, I am getting is below:
[NameValuePair(key=Server, value=GitHub.com), NameValuePair(key=Date, value=Mon, 05 Sep 2022 07:53:41 GMT), NameValuePair(key=Content-Type, value=application/json; charset=utf-8), NameValuePair(key=Transfer-Encoding, value=chunked), NameValuePair(key=X-OAuth-Scopes, value=admin:enterprise, admin:gpg_key, admin:org, admin:org_hook, admin:public_key, admin:repo_hook, delete:packages, delete_repo, repo, user, workflow, write:discussion, write:packages), NameValuePair(key=X-Accepted-OAuth-Scopes, value=), NameValuePair(key=X-GitHub-Media-Type, value=github.v3; format=json), NameValuePair(key=X-RateLimit-Limit, value=5000), NameValuePair(key=X-RateLimit-Remaining, value=4946), NameValuePair(key=X-RateLimit-Reset, value=1662367828), NameValuePair(key=X-RateLimit-Used, value=54), NameValuePair(key=X-RateLimit-Resource, value=core), NameValuePair(key=Access-Control-Expose-Headers, value=ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset), NameValuePair(key=Access-Control-Allow-Origin, value=*), NameValuePair(key=Strict-Transport-Security, value=max-age=31536000; includeSubdomains; preload), NameValuePair(key=X-Frame-Options, value=deny), NameValuePair(key=X-Content-Type-Options, value=nosniff), NameValuePair(key=X-XSS-Protection, value=0), NameValuePair(key=Referrer-Policy, value=origin-when-cross-origin, strict-origin-when-cross-origin), NameValuePair(key=Content-Security-Policy, value=default-src 'none'), NameValuePair(key=Vary, value=Accept-Encoding, Accept, X-Requested-With), NameValuePair(key=X-GitHub-Request-Id, value=77D2:7B0D:1C580A:203694:6315AB04)]
Here, we can see that X-RateLimit-Remaining's value=4946. So, the rate limit is remaining but still create operation is blocked.
What is the reason for this blocking? And is there a way from the header from which I can identify the failure cause? How I can differentiate this blocking from the normal rate limit exceeding blocking?
Beta Was this translation helpful? Give feedback.
All reactions