Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Auto Close policy after deduplication count reaches 100.

I have a notification policy that applies to all alerts where notifications are delayed unless the alert occurs 10 time within 11 minutes and also has an Auto Close policy for 10 minutes after the last occurence.

The problem is that, if an alert is not resolved and reaches a deduplication count of 100 (the maximum before the count stops going up), the auto close policy kicks in and closes the original alert and a new alert gets created, thus restarting the notification policy and resending notifications about every 2 hours.

Is there a way to fix this or get around it? Preferably, the auto close policy would not activate even if the deduplication count is 100 seeing OpsGenie is in fact still receiving alerts, just not increasing the deduplication count.

2 answers

Would be great to get this auto-close feature, or continue counting past 100. I'd prefer the auto-close.

0 votes
Brennan Kiely
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 10, 2020

Hi Bogdan,

Right now, this functionality can't be changed. However, we do have a feature request to keep counting the alerts past 100 for the auto-close policies. The ticket number for this is ALX-3024. We don't have an external-facing Jira to track these, but you can reach out to us and reference that number if you're looking for an update in the future.


Hi Brennan,
Thank you for your response. It's too bad that we cannot do this for now, but we will wait. In the mean time, is there any way to mitigate or get around this using other OpsGenie features?

- Bogdan

Brennan Kiely
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 11, 2020

Unfortunately, there isn't a great workaround for this right now. You could probably rig something up with OEC to run some custom scripts to handle this differently, but it's really probably more trouble than it's worth to go through. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events