Legacy automation rule SLA breached triggers twice

Issue Summary

A race condition with multiple rules triggered SLA breach across Legacy Automation and A4J leads to the SLA rule being executed twice. 

Steps to Reproduce

Since it's a race condition, it's not possible to consistently reproduce this. It may be reproducible if multiple rules are set up across Legacy Automation and A4J to trigger on "SLA Breach" events that lead to issue changes.

It might also be worth investigating to see if multiple legacy automation rules could cause this as the support investigation was not able to determine exactly which issue change event lead to the race condition.

Expected Results

The rule executes once. 

Actual Results

The rule is executed multiple times. 

...

Workaround

This can be avoided if a single rule is set up as that would mean there wouldn't be parallel issue change actions happening.