Custom object process always auto-starts when the condition is to auto-start on Update, when the value of a lookup custom attribute is different than the previous one, even if the value has not changed. This occurs from both the UI and from XOG, even if the attribute is not even included in the request.
Steps to Reproduce:
Expected Results: The process does not trigger, as the custom_attr value has not changed.
Actual Results: The process will trigger.
Release : 15.9.3, 16.0.0, 16.0.1, 16.0.2
Component : Clarity XOG and REST API
Targeted Fix in Release 16.0.3