We’re seeing the same interaction event fire twice to our SQS queue via EventBridge, usually within 50ms. The event IDs match perfectly. I’ve added a simple dedup check in the Lambda handler using the id field, but it’s getting messy with race conditions. Is there a standard way to handle this on the Genesys side, or am I stuck building a distributed lock? Here’s the payload structure I’m parsing:
{"id": "evt-123", "detail": {"eventType": "conversation-participant-added"}}