{
"id": "evt-123-abc",
"detail": {
"type": "conversation:update",
"resourceId": "conv-456"
}
}
Seeing this payload twice for every single conversation update in our SQS consumer. The id is identical, but the timestamp in the outer envelope differs by about 500ms.
We’re using the standard EventBridge rule setup via the Genesys Cloud console. I’ve checked the API docs for PUT /api/v2/integrations/eventbridge/rule/{id} and there’s no obvious “dedup” flag. Is this a known Genesys quirk or am I missing a config option?
Tried:
- Adding a unique key based on
detail.resourceId+detail.typein the Lambda. It works but feels hacky. - Checking if the
detailTypematches. It does.
The duplicate hits are messing up our state machine logic. If anyone has a clean way to handle this on the consumer side without rewriting the whole handler, let me know. Just looking for the standard pattern here.