I'm trying to automate when we are going to breach the daily/hourly service limit in automations. I know it queues up breaches and notifies every hour when there is a breach. But right now, when my rule runs with the Service Limit Breached trigger, we can get multiple notifications all at once with the same top 5 offenders. It will just empty out the queue so the number of notifications varies.
I'm trying to avoid getting all those duplicate messages so I can create a work item for us to investigate. Is there any way to limit this so we only get 1? The rule is really simple but I can't seem to attach a screenshot of it.
Any and all ideas are welcome.
Hi Lori
That’s a great question — this is a common challenge when working with Service Limit Breached triggers in Jira Automation. Since those events are queued and can batch-fire together, multiple notifications for the same offenders are expected behaviour by design.
To reduce duplicates, here’s what has worked well for me:
1-Use a conditional check before sending the alert - for example, add an “Issue fields condition” or “Advanced compare condition” that verifies whether a breach-related work item already exists within a defined time window (e.g., 1 hour).
2-Leverage smart values like {{createdIssue.key}} or custom fields to store the timestamp or unique identifiers of recent breaches, then skip any automation runs that match those values.
3-Alternatively, you can centralize alerts via a dedicated “Breach Tracking” issue type or queue - the rule only creates or updates that single issue instead of generating new ones every time.
This setup ensures you only get one actionable notification per time frame while maintaining full visibility of recurring offenders.
Hope this helps streamline your process with best time management - it made a big difference for our internal monitoring rules!.
Best Regards
A.A Silkina
Awesome, thanks for the suggestions Ayyan! I'll give it a shot.
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.