Rate-limit: Header retry-after not computed correctly

Hello,

We are handling the Atlassian rate limit by using the retry-after header, available when Atlassian answers with a 429.

Since this morning, the retry-after value is “1”. This is making our app to retry those requests immediately after.

Is this happening in your instances?

Best,

Paulo Alves.

2 Likes