Did someone found a way to understand the Jira instance reaching the limit, from the warning email received?
(yes, I have many Jira instances, and I guess I'm not the only one)
That email notes reaching the monthly usage limit, and so that is likely the count of rule executions which count. Not all rule actions count, and so first review this information:
https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update
https://support.atlassian.com/cloud-automation/docs/automation-service-limits/
Then navigate to the global rules list for each Jira instance, checking the Usage area as that will indicate which one had the problem.
It is possible you have a single rule with errors, looping, etc. that caused the problem. The new packaging distributes the usage limits based on products, license level (i.e., Free, Standard, Premium, or Enterprise) and user license counts. Reviewing the global usage and logs will indicate where the problem occurred, or if your automation usage has recently changed.
Kind regards,
Bill
Hello @David Berclaz _Apwide_
I have not yet received one of these messages. I assume there is nothing in the email header or elsewhere that identifies the specific instance, correct?
If you click on the Upgrade button, does it take you to the Manage Subscription page for the specific instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.