We have configured the AWS EventBridge integration to capture real-time Genesys Cloud events. The routing:queue:member:added event arrives at the Lambda consumer, but the JSON payload lacks the conversationId field required for our downstream processing. The event structure only contains the memberId and queueId. Is this expected behavior for this specific event type, or is the integration missing a configuration flag?
{
"source": "genesys.cloud",
"detail": {
"memberId": "12345",
"queueId": "67890",
"timestamp": "2023-10-27T10:00:00Z"
}
}