Resolve Email Request Failures due to Rate Limit in JSM Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
If your custom email isn't processing, check the email connection. The connectivity log may show "Rate Limited" statuses.
Diagnosis
Go to Project Settings > Channels & self service > Email Request.
Click View Logs for the affected email.
Click Connectivity Log and it will show as per the screenshot:

Cause
The email processor will try to pull messages from your mail server every minute, so even though it fails, it will likely connect on the next try. When the connection between Jira and the mail server fails many times, Jira no longer tries for a certain amount of time, and this time increases if it fails again. Hence you notice multiple error logs mentioning "Retrying in xxx minutes".
This issue typically arises when OAuth fails to retrieve the appropriate access token necessary for integrating the service management project with a custom email account such as Microsoft or Google.
Solution
Get a screenshot of the connectivity logs. This will be handy if you want to track when the email starts failing.
Click on the Action menu (⋯) and select the Remove option.
Note: If your custom mail handler is configured as the Reply-to address, you will need to change this to a different mail handler before the remove option is available.
To reconnect the account, click the Add external email button.
Then, click the "Microsoft" or "Google" symbol to reconnect it using OAuth. For more information about this, refer to Switch your Microsoft and Google email accounts to OAuth documentation.
Once reconnecting, monitor the email connectivity and processing logs.
When you successfully reconnect, emails that were previously received and in unread status will not be processed. Please contact support along with a timestamp from when it started to fail so that we can manually get them processed.
Was this helpful?