Is there a standard pattern for handling duplicate events from Genesys Cloud via EventBridge? The detailType and source are identical for retries, and the conversationId isn’t unique enough if the event fires twice.
{
"id": "a1b2c3",
"detailType": "ConversationUpdated"
}
We’ve tried using event.id as a DynamoDB key, but it feels fragile. How are you handling this in your Terraform-deployed consumers?