The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
As per Atlassian documentation, APIs should be sending "Retry-After" header during 429 Error throttling scenarios.
However, upon testing we have figured that, asset endpoints like say https://api.atlassian.com/jsm/assets/workspace/<workspaceId>/v1/objectconnectedtickets/<objectId>/tickets etc. are not returning "Retry-After" header during 429 Error throttling scenarios.
Any idea why ?
1 answer
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.