How to Prevent Duplicate Jira Automation Runs?

Question

I have an automation rule that can be triggered when multiple fields on the same Jira issue are updated around the same time. Occasionally, the rule seems to run more than once and creates duplicate actions.

What is the best way to prevent this? Is there a recommended trigger condition, delay or other method to make sure the automation only processes the issue once?

Gabriela - LeanZero · Answer

Hi Raxa, Carlos has the why, separate updates start separate runs, so I'll add what I saw when I tested the usual fix on a test site today. The guard most people reach for is a condition that a label such as processed is absent, with that label added as the very first action. It held when the updates were five or more seconds apart, but when two updates arrived under a second apart, both runs passed the check before either had added the label, three times out of three, so on its own it won't stop a tight burst.

If your duplicates are rare and spread out, I think the guard is enough. If they come in bursts, I'd move the work to a scheduled rule that picks up matching items with JQL and marks each one done, since each item is then handled by one scheduled run and not by a burst of triggers. A Delay would only help if the rule checks the flag again after it, and it's Premium or Enterprise only.

Your audit log will show whether the duplicate runs start within a second of each other. What's making the field changes?

Carlos Garcia Navarro · Answer

Hi @Raxa ,

Jira automation can run once for each update event. If several fields are saved in separate updates, a broad Work item updated trigger can start several runs close together. Atlassian recommends using a more specific Field value changed trigger when possible; you can choose which fields and edit operations it monitors.

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers

Nikola Perisic · Answer

Welcome @Raxa

Are you using Jira Premium? If so, adding a delay action or splitting the rule into smaller pieces can help prevent duplicate runs.