Docs state: “The event pattern must match the structure of the event payload exactly.” I’m trying to wire up a simple consumer for conversation events, but the rule just sits there doing nothing. The pattern looks identical to the sample event I got from the console, down to the source and detail-type. Here is the rule configuration I’m using:
{
"source": ["genesys.cloud.conversations"],
"detail-type": ["Conversation Created"],
"detail": {
"eventType": ["conversation.created"]
}
}
I’ve verified the event bus is the default one and the IAM role has events:PutEvents permissions. The target is a simple Lambda that just logs the input. Nothing shows up in CloudWatch. I even tried widening the source to genesys.cloud.* with no luck. It feels like the detail payload structure might be slightly off, but the docs don’t show the full nested JSON for conversation.created. Is there a way to dump the raw event to a dead-letter queue or a log group just to see what’s actually hitting the bus? The standard debug logs are empty because the rule never triggers.
The timestamp on the event seems correct, and I can see the conversation being created in the Genesys Cloud UI. I’m assuming it’s a case sensitivity issue or a missing nested field in the detail object. I’ve checked the EventBridge console for failed deliveries, but since the rule doesn’t fire, there’s nothing there. I’m stuck guessing which part of the pattern is wrong. The documentation for custom events is sparse on the exact schema for detail. Any pointers on how to inspect the actual event payload without a working rule? I need to see the raw JSON to adjust the pattern.