Issue Summary

Customers are experiencing discrepancies between automation rule failure notifications and the audit log. The Audit log shows the rule execution status as 'no actions performed' despite the trigger conditions being met. Whereas the customer gets a notification email stating that the rule execution has failed. In backend logs, the Rule execution has a status of Throttled. 
This is confusing customers as to why the rules are failing to execute, and they are not able to figure out the exact time Throttling is kicking in for the Automation rule execution. 

Steps to Reproduce

1. Create an Automation rule that makes bulk changes to multiple Jira work items. 
2. Once the Automation rule execution hits the daily processing time limit for automation, the rule execution is stopped. 

Expected Results

In the Audit log, we should see the correct status for the Automation rule execution restriction/failure. If the rule is throttled due to the daily processing time limit, then we should see the Throttled status in the Audit log.

Actual Results

The admin gets a notification email that the rule execution has failed, but in the Audit log, we can see the status no actions performed for the failed execution of the Automation rule. 

Workaround

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