Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Asset management APIs are not returning "RETRY-AFTER" header in throttling 429 error scenarios

Nijas Rawther
Nijas Rawther March 11, 2024

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 ?

Answer
Watch
Like Be the first to like this
261 views

1 answer

0 votes
Marc - Devoteam
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
March 11, 2024

Hi @Nijas Rawther 

I would address this issue with Atlassian Support.

But it also could be that this doesn't apply on this API part as assets (formerly Insight), is not completely integrated.

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Desk
Jira Service Management
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events

    See all events