Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I'm not able to get retry-after header on getting 429 Edited

Screenshot 2021-04-06 at 5.35.02 PM.png


As mentioned above picture, I should get these headers in response when I receive 429, but I'm not getting these headers.

Here are the status code and response headers that I'm getting:

server: 'AtlassianProxy/',
vary: 'Accept-Encoding',
'content-type': 'text/html;charset=ISO-8859-1',
'strict-transport-security': 'max-age=315360000; includeSubDomains; preload',
date: 'Tue, 06 Apr 2021 12:03:12 GMT',
'atl-traceid': 'caa2c0619953d843',
'x-xss-protection': '1; mode=block',
'x-envoy-upstream-service-time': '15',
'x-content-type-options': 'nosniff',
connection: 'close',
'expect-ct': 'report-uri="", enforce, max-age=86400',
'content-length': '1922'

1 answer

0 votes
Andy Heinzer Atlassian Team Apr 07, 2021

Hi @Lalit Kumar 

Sorry to hear about this problem.  However I believe that the documentation you are referring to here is for our Jira Server/Data Center editions as seen in

However this Community posts makes it appear that you might be using Jira Cloud instead. For Jira Cloud, we have documented the rate limit behavior a little differently over in in that page the exact wording is

Retry-After headers

429 responses may be accompanied by Retry-After and X-RateLimit-Reset headers.

Retry-After indicates how many seconds the app must wait before reissuing the request. If you reissue the request before the retry period expires, the request will fail and return the same or longer Retry-After period.

X-RateLimit-Reset indicates the date time when you can retry the request. It’s provided in the format: yyyy-MM-ddTHH:mmZ.

Some transient 5XX errors are accompanied by a Retry-After header. For example, a 503 response may be returned when a resource limit has been reached. While these are not rate limit responses, they can be handled with similar logic as outlined below.

As such, not all the same headers are included in the Cloud REST response and not all 429 responses will include a retry-after in the response Cloud. 

The rate limiting in Cloud is continuously evolving based on numerous factors.  Hence you are not as likely to get this specific header in Cloud as you might get back from a Server/Data Center edition.  Instead our Cloud rate limiting documentation suggests applying a jitter to the delay and using an exponential backoff strategy if you are creating an app to make such REST API calls.

I hope this helps.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

98 views 2 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you