We’ve got an EventBridge rule set up to catch conversation:wrapup events, but it’s dead silent. The target Lambda function isn’t triggering, and the CloudWatch logs for the rule show zero matches over the last hour, even though we’ve manually wrapped up several test conversations in Genesys Cloud.
Here’s the event pattern JSON we’re using:
{
"source": ["genesys.cloud"],
"detail-type": ["Event"],
"detail": {
"eventType": ["conversation:wrapup"]
}
}
I’ve verified the event bridge configuration in the Genesys Cloud admin console. The destination is active, and the ARN matches the target Lambda. I also checked the /api/v2/events/webhooks endpoint to confirm the webhook is enabled and returns a 200 OK status.
Troubleshooting steps taken:
- Confirmed the Lambda function has the correct IAM role to receive events from EventBridge.
- Checked the Lambda logs; they’re empty, which confirms the event isn’t reaching the function.
- Tried a broader pattern by removing the
detailblock entirely, just matching onsourceanddetail-type. Still nothing. - Verified the timezone settings in our org match the event timestamps.
- Used the
/api/v2/events/webhooks/{webhookId}/testendpoint to send a test event. The test worked, and the Lambda fired. This suggests the connection is valid, but the live events aren’t matching the pattern.
The weird part is that the test event payload looks exactly like what we expect in production. Is there a known issue with conversation:wrapup events not propagating to EventBridge immediately? Or are we missing a field in the pattern?
Also, I noticed some documentation mentions conversation:analyzed events firing differently. Could the wrapup event be batched or delayed in a way that breaks the real-time expectation? We need this for near-real-time analytics, so any latency issues would be a blocker.
Any ideas on how to debug the event pattern further? We’re stuck.