Sometimes SLA based automation rule is not triggered when an SLA level is breached

Issue Summary

Sometimes SLA based automation rule is not triggered when an SLA level is breached.

This happens randomly in the system 

Steps to Reproduce

This is not reproducible because this happens due to intermittent inconsistencies in the backend systems. The occurrence , though very rare, leads to the automation rule getting skipped from triggering. 

Expected Results

Automation rule (if configured) should be triggerred when SLA is breached

Actual Results

Automation rule is not getting triggered

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available