Issue Summary

Whenever a series of rapid (~1 second or less) updates occur to an Assets Object, rules that are triggered by these events may or may not get the correct information for when the event occurred.

Steps to Reproduce

1. Create an Automation Rule with the Object Trigger set to Updated.
2. Add an Action Component for the Log Action to log object.updated which will return the DateTime the Object was updated.
3. Update an Object's Attributes with ~1 second intervals at least 6 times.

Expected Results

The smart value object.updated should return the information in the moment the event occurred that triggered the rule. i.e. the correct value, in every case.

In the case of 6 events at ~1 second intervals, object.updated should show something like:

2024-10-20T16:45:44.8+0000
2024-10-20T16:45:45.9+0000
2024-10-20T16:45:47.0+0000
2024-10-20T16:45:47.9+0000
2024-10-20T16:45:48.9+0000
2024-10-20T16:45:50.1+0000

Actual Results

Instead, the smart value object.updated returns values depending on when the rule itself manages to actually run:

2024-10-20T16:45:44.8+0000
2024-10-20T16:45:45.9+0000
2024-10-20T16:45:47.0+0000
2024-10-20T16:45:47.0+0000
2024-10-20T16:45:47.0+0000
2024-10-20T16:45:50.1+0000

This is indicated by there being multiple entries in the Audit Log with the same value despite the Rule executions for those two audit logs occurring at different times (~1 second apart).

This is intermittent. It does not always happen, but it does frequently when the conditions are right.

Workaround

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