EventBridge deduplication: handling duplicate Genesys Cloud interaction events

Seeing double events in our queue for every Genesys Cloud interaction update. The payload looks identical except for a new EventId.

{ "detail-type": "Interaction Update", "source": "genesyscloud", "detail": { "id": "123" } }

Can’t rely on detail.id for deduplication since it’s the same. Should I hash the whole detail block or is there a specific event-id field I’m missing? Trying to avoid processing the same trace span twice in our OTel collector.