Automation Error - Limit is Reached - E-mail sending has been disabled globally

[Jan Michelle Lamboso]

Hey community!

I was testing a single automation rule I created under my free cloud. But after the rule successfully sent two emails, I hit below error --

E-mail sending has been disabled globally due to limits reached in the last 24 hours (if you just signed up your sending limit will increase automatically over the coming days). Please contact Atlassian Support if you need more help!

I checked Global Automation settings > Usage tab to see if there are any global emails getting sent other than the ones from my automation rule but I can't find any.

Have you got any idea why this is happening? 

Thanks so much!

[Sakina Shabanova]

Hi Jan, I am facing the same issue. 
Currently trying to find a way to turn off notifications . So far couldnot yet. 

Were you able to manage resolution in his way? Do you know if it is possible to stop Jira sending notifications and count only emails?

Thanks in advance, 

Sakina

[Trudy Claspill]

@Sakina Shabanova 

You can turn off notifications by disabling outgoing email from System / Outgoing Email.

https://<yourURL>/secure/admin/OutgoingMailServers.jspa

That disables only notifications generated by the notification configurations for projects. But it does disable ALL notifications, which doesn't seem like a good plan for your environment. Users won't get any updates about new issues or changes to issues.

[Trudy Claspill]

Hello @Jan Michelle Lamboso 

According to documentation provided by Atlassian, on the Jira Free plan there is a limit of 100 notification emails per day.

As noted in the other answers, the Automation Service Limits also mention a 100 emails limit.

According to an answer from an Atlassian Team member on this post, that limit is actually across the Jira instance and includes both Notifications and emails sent through Automation rules. 

While your automation may have sent only 2 emails, if your project notifications sent 98 over the preceding 24 hour period then that would explain why you received the message.

[Jan Michelle Lamboso]

Hi @Trudy Claspill

Since project notifications count towards my monthly limit, does that not get reflected in the Usage tab? Or is there someplace else where I can see the notification usage as well?  

[Trudy Claspill]

The Usage Tab concerns only Automation Rules.

I am not aware of any report natively available in the Free Jira subscription that will tell you how many Notifications (or overall outgoing emails) have been sent in a time period. 

[Bill Sheboy]

Hi @Trudy Claspill 

I added a comment about email usage to the suggestion for improving features for automation usage management: https://jira.atlassian.com/browse/AUTO-922

Kind regards,
Bill

[Bill Sheboy]

Hi @Jan Michelle Lamboso -- Welcome to the Atlassian Community!

There are rule usage limits and other service limits:

https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update
https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

From what you describe, it is likely you are encountering the Send Email Action limit, which only applies to the Free license: 100 emails in a 24 hour period.

If you review the audit log for the specific rules which have run you may find what is sending the emails to this volume level.

Kind regards,
Bill

[Walter Buggenhout]

Hi @Jan Michelle Lamboso and welcome to the Community!

On the free plan, you can only run a limited number of automation rules per month. For more details on those limits, see this support article.

What is happening here, is what is in the message you shared: the system tries to estimate your usage and thinks you will not be able to stay within limits at the rate your currently triggering the rule. As a result, it blocked additional emails from being sent. It will adjust automatically as the systems learns how your organization is using the automation rule, also letting you know very early on that your setup will probably not scale on the free plan over time, so you can consider this right now, rather than after rolling it out across your team.

Hope this helps!