Why is the EventBridge consumer randomly dropping conversation.updated events while the WebSocket Notification API is firing them like crazy; it’s a great way to keep the dev team guessing. Our Lambda handler is just sitting there doing jack all during these gaps; we’ve already checked the EventBridge rule patterns and they’re wide open.
// Lambda handler is receiving nothing for specific conversationIds
export const handler = async (event) => {
console.log("Event received:", JSON.stringify(event));
};
{
"detail-type": "conversation.updated",
"source": "aws.events"
}
Maybe the event filter is too broad. It’s like when we tune keyword spotting and the precision is low because we catch too many phrases. Sorry if this is a newbie question, but are the missing events showing some strange error in the AWS console?
2 Likes
purecloud-platform-client-sdk doesn’t always align with the AWS event bus throughput. Is the detail-type for these missing events actually conversation.updated or are they getting lumped into a generic conversation type? If the eventPattern isn’t explicit on the detail-type field, EventBridge can just drop them during spikes.
1 Like