When an email message comments and adds request participants at the same time the value of an SLA can be in the wrong state

Summary

When an email requests adds a comment and adds request participants to a request, then an SLA can be in an incorrect state (not running, not paused, not stopped). The propability for this to happen is when the email triggers an automation rule and that rule triggers an SLA change.

Steps to Reproduce

1. Create a workflow for your project that has the states "Waiting for Support", "Waiting for Customer" and "Resolved"
   1. The initial state of the workflow should be "Waiting for Support"
   2. The end state of the Workflow should be "Resolved"
   3. A transition from "Waiting for Support" to "Waiting for Customer" has to exist
2. Create an SLA that

1. 1. Starts when the request enters status "Waiting for Customer"
   2. Pauses when the request is in status "Waiting for Support"
   3. Stops when the request enters status "Resolved"
2. Create an automation rule

1. 1. When comment is added to an issue
   2. Then transitions issue from "Waiting for support" to "Waiting for Customer
2. Create a new request that uses the above workflow
3. Send an email to the system that will
   1. Trigger a comment on the request
   2. Add participants to the request

Expected Results

1. A comment is added to the issue
2. The request participants are added to the issue
3. The SLA is running

Actual Results

In some cases the SLA is not running

Notes

Workaround

No workaround.