Recently we added a guide explaining how rate limiting works in Jira and Confluence. The same guide applies to both Jira and Confluence, but is available in both documentation sets: Jira: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/ Confluence: Rate limiting We realise the…

@dmorrow Another problem with this new approach is in the way Jira identifies the “App + user” call types. In the case of workflow post-functions (or event webhooks for that matter), the action is clearly initiated by the user, completely outside of app control. Therefore, any REST call the app make…

Hi Guys, Thanks for the feedback. There’s some great points that I’d like to address, but I’ll need a few days to work through them. I’m on leave today so I’ll aim for a response mid next week. Regards, Dugald

Hey @dmorrow , would love an update on the points mentioned above. Did you have the time to work through them? Also I’d like to mention that in its current incarnation, the Retry-After header is not very useful. For us, it has only returned values of 60 and 300 seconds for status 429 responses so fa…

I’ve gone through the comments and actioned them by creating issues. Here’s a summary of all the issues, including the few I raised previously: ACJIRA-2555 & CONFCLOUD-71116 : As an app developer, I need to know the rate limits that my app is subject to ACJIRA-2554 & CONFCLOUD-71203 : As an app de…

Hi @dmorrow , [AC-2542] - Ecosystem Jira is not visible to non-Atlassians. Thanks, David

Thanks @david2 , I’ve fixed this now.

In addition to my previous response, there are a number of issues relating to inconsistent and invalid error codes returned when limits are reached under various scenarios: ACJIRA-1892: Bulk create issue results to status 503 for some instances ACJIRA-1913: Some instances receives response errors …

@dmorrow apologies if this should be a separate topic but this felt like the most appropriate place to begin… A few days ago we received 4x the number of webhooks per hour than usual, triggered, as far as we can tell, by a single tenant. We usually see peaks of 500,000 webhooks per hour from Atlass…

Hi @jbevan , Thanks for raising this. I agree we need to put a solution in place that will avoid this type of incident occurring in the future. I’ve created ACJIRA-2497 and will reach out to the Jira Ecosystem team to see if they can prioritise it. Regards, Dugald

Any traction on this internally? We can’t just return 429s when we get spikes in inbound webhooks because we’ll violate our Fortified Apps SLA if I understand things correctly… Recent examples of individual tenants making waves in our infra: [Screenshot 2022-01-18 at 17.32.44]