We are getting status code 429 in Jira lower environment but not in production Jira

[Amit kundu]

HI ,

We are making a callout to Jira from Salesforce to get the Jira key on our cases. And we are making a 2nd request to Jira if we have any sub task for that Jira key.

Let suppose we make a callout to Jira from our case creation time to get the Jira Key on our case object and then we are checking if any sub task or subkey associated with that jira key then we are making second request to Jira.

let suppose we have 10 sub task to that jira key then we are getting 4,5 success then we are getting status code 429 in response. We are doing this in lower environment on Jira. And on Jira prod we don't get this type of issue.

So do we have different callout limit on Jira for Prod or lower instance?

Endpoint url  > JirabaseUrl+ '/rest/api/2/issue/' + sub_key

[John Price]

This is Jira Data Center, right? Couple of things to check:

1. In Jira, go to Admin -> System-> Rate Limiting and check the values in prod and test environments. You can also check who's being limited - see https://confluence.atlassian.com/adminjiraserver/improving-instance-stability-with-rate-limiting-983794911.html 
2. If that seems OK, check the Jira server logs to see what exactly is going on. If you have a reverse proxy like nginx, maybe that's involved.
3. It could be that your test environment is less robust than prod (fewer servers, lower server memory, etc.) and so you are getting errors due to that maybe?

Also you should look at https://confluence.atlassian.com/adminjiraserver/adjusting-your-code-for-rate-limiting-987143384.html and add some defensive coding against this problem. Jira sends back rate limit info in response headers with every call and you can just add a checkRateLimit() function or something.

Good luck!