-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
9.12.8
-
9.12
-
5
-
Severity 2 - Major
-
41
-
Issue Summary
When recieving a 401 or 403 response from GitHub due to hitting their secondary rate limit, Jira continues to try and sync the repo, resulting in repeated errors.
This is reproducible on Data Center: yes
Steps to Reproduce
- Have a very large repo on Github Cloud that is attempting to sync to Jira
- Hit the secondary rate limit, and have the error returned be a 401 or 403 response code
Expected Results
Jira code will attempt to take successful corrective action to prevent the looping error and stay under the rate limit, as it does when getting a 429 response
Actual Results
Jira continues to attempt to sync the repo, resulting in repeated errors like below in the atlassian-jira.log (may instead be a 401 error, as well):
Caesium-1-1 WARN ServiceRunner
[c.a.j.p.d.spi.github.GithubClientWithTimeout] Failed to execute request [<REPO NAME>] response code: 403, errors:
You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID #####. (403)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
-
- Gathering Impact
-
- links to
- mentioned in
-
Page Failed to load