We noticed that we can easily reproduce a loop when we change a field value two times in a second frame when there is an automation rule associated with that field. In order to avoid this, and we also believe this is the reason why we have other issues with Exalate, we’d like to condition our code to not process events for Automation for Jira user. Do you know if this is possible? I will resume the issue we have here:

1. We change the field A value from No to Yes.
2. Automation evaluates the field and update a field that is not part of the sync.
3. Immediately change again Yes to No.
4. Automation evaluates again the field and update the field related to this rule.
5. The mirrored field A in the remote instance updates from No to Yes.
6. Automation also evaluates the field value in the remote instance and trigger an event to the origin instance with the field updated to Yes.
7. Here is where starts looping, because we have changed in the step 3 the value from Yes to No, and the new event generated by Automation on the remote side changes again the Field A value from No to Yes.

Hope is understandable enough, if not, please let me know.