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 ?
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.
It looks like you're new here. Sign in or register to get started.
