Maximum expected retry-after header value

Jira Development Jira Cloud
,
1

Hello,

Following on from Marketplace Partners: API rate limiting for free apps Quick Reference Guide I’ve taken a closer look at the headers Atlassian are responding with in REST API calls.

What is the maximum expected retry-after header value we should receive from Jira Cloud or Confluence Cloud?

I can see values as high as 1652 (7 times for one customer), 1425 (1 time for one customer), 2157 (1 time for one customer) and 3089 (1 time for one customer) which seem a little extreme.

For some customers we regularly see retry-after header values in the 200s.

Tagging @KelseyVanScoy as I know you’re working in this area.

1 Like
2

Hi @jbevan can you please raise a support ticket here and share it with me once you open it? I want to ensure quick follow up for you. Thank you

3

The retry-after header is a value in seconds. Given our quota rate-limit has a max time-window of one hour as written here, the max value someone could receive is 3600.

Yes, this is indeed incredible long and we internally would like to transition to an alternative solution that would provide much shorter retry-after values.

From the support ticket I raised, for posterity.