purecloud-platform-client-sdk isn’t reflecting the same event stream as the Notification API. The EventBridge rule is configured for conversation.participant.update, but the Lambda target isn’t receiving any payloads when a participant’s employeeId changes during a transfer.
The logs show the rule is active, yet the event just vanishes. Tried checking the eventId via GET /api/v2/outbound/events/{eventId} for related dialer triggers, but that’s a dead end.
The eventBody is populated in the WebSocket stream, but EventBridge stays silent. It’s basically doing jack all for this specific event type.
Right, EventBridge is notoriously inconsistent compared to the Notification API, tbh. If the conversation.participant.update event isn’t hitting the Lambda during a transfer, it’s usually because the employeeId change isn’t triggering a state change that EventBridge recognizes as a publishable event. iirc, some participant updates are swallowed if they don’t alter the participant.status or participant.role.
The purecloud-platform-client-sdk is just a wrapper; it won’t fix a missing event at the bus level. If the rule is active but the payload vanishes, check the event pattern. You’re probably filtering too tightly on the detail-type. Try broadening the pattern to capture any conversation event and then filter the employeeId logic inside the Lambda instead of relying on the EventBridge rule to do the heavy lifting.
If that still fails, it’s likely a timing issue where the update happens too fast for the bridge to catch it before the participant is detached during the transfer, imo. You might have to fallback to polling /api/v2/conversations/{conversationId}/participants/{participantId}/wrapupcodes or other participant endpoints if you need to verify the final state of that employeeId after the transfer completes. afaik, there’s no way to force EventBridge to be more granular with these specific updates.
The point made in the earlier reply is correct. The API INTEGRATION pipeline often fails to trigger this event if the EMPLOYEE_ID change occurs during a specific transfer state. It’s common for the event to be suppressed if the participant’s state doesn’t transition.