Facing 429 error after integrating Whatsapp and Jira Service Management.
We have integrated Jira Service Management & whatsapp using the REST API functionality available in JIRA. It is successfully integrated & after one month of our launch on the production activity, we are facing 429 error for some type of requests we are raising. Error mentioned as below
Error :
b'<!DOCTYPE html><html lang="en"><head><meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge"><title>Oops -
an error has occurred</title><link type=\'text/css\' rel=\'stylesheet\' href=\'/static-assets/metal-all.css\' media=\'all\'><script src=\'/static-assets/metal-all.js\'>
</script><meta name="decorator" content="none" /></head><body class=" error-page error429">
<script type="text/javascript">document.body.className += " js-enabled";</script><div id="page"><header id="header" role="banner">
</header><!-- #header --><section id="content" role="main">
<div class="aui-page-panel"><div class="aui-page-panel-inner">
<section class="aui-page-panel-content lowerContent"><div id="error-state">
<span class="error-type"></span><h1>Something went wrong</h1><p>Try reloading the page, then check our <a href="https://status.atlassian.com">
Statuspage</a> for any current outages. If there are no relevant outages, create a <a href="https://support.atlassian.com/contact/">support request</a>
so we can help you out.</p><p>If you create a request, include the following so we can help you as fast as possible:</p><ul>
<li>Error type: <strong>429 - Too many requests</strong></li><li>Log reference: <strong>6ddc5293-63f5-44ef-a2bb-70fd05db576a</strong></li></ul></div></section>
<!-- .aui-page-panel-content --></div><!-- .aui-page-panel-inner --></div><!-- .aui-page-panel --></section><!-- #content --><footer id="footer" role="contentinfo">
<section class="footer-body"><div id="footer-logo"><a href="http://www.atlassian.com/" rel="nofollow">Atlassian</a></div></section></footer><!-- #footer -->
</div><!-- #page --></body></html>'
When reached out to Atlassian team for the same, They mentioned that it is happening due to rate limit issue for a particular user.
Can anyone please suggest on how to resolve this as at present it is impacting my production environment.
Thank you in advance.
