Improve audit event collation behavior

What is the challenge?

• History audit events for a record are grouped using a sliding 5-minute window. If multiple audit events happen within 5 minutes of each other, the UI later collapses them into a single grouped history record instead of preserving each event as a separately visible entry.

• This is especially confusing for automation-driven status changes. A record can briefly move through an intermediate status, but once the collation job runs the history tab may only show the grouped event with the start and end values, making it appear that the intermediate transition never happened.

• The grouping does not occur immediately. It runs no earlier than 5 minutes after the last event in the group and can happen later depending on queue timing, so users may see separate entries at first and then see them merged later.

What is the impact?

• Customers and internal teams can interpret this as inconsistent or incorrect history data because screenshots taken earlier may show multiple automation events while the same record viewed later shows only one grouped event.

• This makes troubleshooting workflow automations harder because the history tab does not clearly expose the constituent audit events that led to the final grouped record.

• Support and product teams need to explain backend audit collation behavior manually, which increases confusion and slows case resolution.

Describe your idea.

• Improve the history tab so users can expand a grouped audit record and inspect the underlying individual audit events in sequence, including intermediate values and timestamps.

• Preserve the grouped summary for readability, but make the grouped state explicit and provide a clear indication that collation is asynchronous and may occur after a delay.

• This would help users understand why a record initially showed multiple events and later showed one grouped entry, while still keeping the history tab compact by default.