We’ve been ingesting Genesys Cloud events via EventBridge into our custom agent desktop backend for the last six months without issue. Suddenly, over the weekend, we started seeing duplicate ConversationUpdated events for the same interaction. The id field in the event payload is identical, but the timestamp is slightly different, usually by a few milliseconds. This is breaking our state reconciliation logic because we process these events sequentially and expect idempotency based on the event ID.
I’ve checked the EventBridge rules and the target Lambda function. The Lambda is returning a success response, so there’s no retry happening on the AWS side. The issue seems to be upstream in the Genesys Cloud to EventBridge integration. Here’s a sample of the duplicate payload:
{
"id": "abc-123-def-456",
"timestamp": "2023-10-27T14:30:00.000Z",
"type": "conversation.updated",
"data": {
"interaction": {
"id": "xyz-789",
"type": "voice"
}
}
}
And the duplicate:
{
"id": "abc-123-def-456",
"timestamp": "2023-10-27T14:30:00.005Z",
"type": "conversation.updated",
"data": {
"interaction": {
"id": "xyz-789",
"type": "voice"
}
}
}
I’ve tried filtering on the Lambda side using the event ID, but that’s a band-aid. I need to know if this is a known issue with the EventBridge integration or if there’s a specific header or field I should be checking to ensure I’m only processing the latest state. I’ve looked through the developer docs and the community forum, but haven’t found a clear answer on deduplication strategies for EventBridge consumers. Has anyone else hit this? Is there a way to configure the EventBridge rule to deduplicate before it hits the target?
We’re using the standard EventBridge integration, no custom API calls involved in the event generation. Just wondering if there’s a best practice here or if I need to open a support ticket. Any insights would be appreciated.