Issue Summary

• When updating an Assets object attribute via the Update object API, if the new value is the same as the current value, the Modified date on the object is updated, but no corresponding entry is recorded in the Activity history for that object.
• This leads to inconsistency between the object’s Modified date and the visible activity timeline.

Steps to Reproduce

• Create or identify an Assets object with an attribute set to an initial value.
• Use the Update object API to change that attribute to a different value and confirm Activity + Modified date reflect this update.
• Call the same API again for the same object, setting the same attribute to the same value it already has.
• Open the object in the Assets UI and check the Activity tab and the Modified date.

Expected Results

• The Modified date and Activity history remain consistent.

Actual Results

• The UI shows a modification time with no corresponding Activity record.

Workaround

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