Duplicate eventbridge events for .acd.end topic

I'm seeing 2 events coming through for v2.detail.events.conversation.{id}.acd.end events. The eventTime and correlationId are the same for both events but the timestamp on the detail is different by ~20ms. This looks like it is happening for all acd end events. I'm not yet seeing duplicates on other participant types but I'm only working with a small test org right now.

There are a couple field differences such as "acdOutcome" and "answeredUserId" are not set in the first event, but are in the second.

First event:

Second Event:

I would expect that for acd END that i would only see one END event, is this expected to see multiple end events? If so, under what circumstances should we expect to see multiple and is there any way to know which end event will be the last one.

Thanks!

@joe.fruland @Becky_Powell, any thoughts here?

This is expected and intentional behavior – we will fire a new end event if something in the conversation changes – like acdOutcome and answeredUserId changing and populating, in this particular case.

The best way to determine the last end event is to look at the timestamp.

Thanks!