Getting a 1005 Close Code immediately after the first batch of events arrives. Trying to wire up the Notification API WebSocket to capture conversation events for OpenTelemetry tracing. The goal is to propagate the trace context from the incoming WebSocket frames into our Data Action spans.
Using the Python SDK to establish the connection:
client = PureCloudPlatformClientV2()
client.set_base_url('https://api.mypurecloud.com')
client.set_auth_provider(oauth2_client_credentials_provider)
notification_client = client.notification_client
notification_client.connect(
topics=['conversation'],
on_event=process_event
)
The connect method returns successfully, and I receive the initial subscription confirmation. However, once the first actual conversation:update event hits, the socket closes unexpectedly. The backend trace shows the span ending abruptly. No specific error message in the payload, just the clean disconnect.
Is there a timeout or message size limit I’m missing? The events are small, just standard conversation metadata. Looking for a way to keep the socket alive while injecting the trace ID into the response headers of the subsequent API calls triggered by these events.