I’ve got an EventBridge rule set up to catch conversation events from Genesys Cloud, specifically the ConversationUpdated event. The rule is configured with a standard event pattern, but it just doesn’t fire. I’ve verified the event bus is receiving data from Genesys, and I can see other custom events hitting the target Lambda, so the connection is fine. It’s just the conversation events that are ghosting me.
Here’s the event pattern I’m using in the rule:
{
"source": ["genesys.cloud"],
"detail-type": ["Conversation Updated"],
"detail": {
"eventType": ["conversation.updated"]
}
}
I’ve also tried relaxing the pattern to just match the source:
{
"source": ["genesys.cloud"]
}
Even with the broad pattern, the rule doesn’t trigger for conversation updates. I’m using a test event from the Genesys Cloud event simulator, and the payload looks like this:
{
"id": "12345",
"source": "genesys.cloud",
"detail-type": "Conversation Updated",
"detail": {
"eventType": "conversation.updated",
"conversationId": "abc-123",
"status": "active"
}
}
The simulator says the event matches the pattern, but when I trigger it through the actual Genesys Cloud interface, nothing happens. I’ve checked the CloudWatch logs for the target Lambda, and there’s no invocation. The rule status is enabled, and the target is confirmed. I’m stuck. Is there a known issue with the detail-type casing or something specific about how Genesys Cloud pushes these events to EventBridge? I’ve looked through the docs, and they’re not clear on the exact event structure for conversation updates. Any ideas on how to debug this further? I’m considering switching to a webhook-based solution, but I’d rather get EventBridge working if possible.