PATCH /conversations/calls losing trace context on queue transfer

Attempting to transfer an active call to a new queue using PATCH on the Conversations API. The operation returns 200 OK, but the distributed trace breaks. The span injected via the traceparent header doesn’t propagate to the downstream queue logic in Jaeger.

Here’s the request payload:

PATCH /api/v2/conversations/calls/{callId}
{
 "state": "transferring",
 "transferTo": {
 "queueId": "12345678-1234-1234-1234-123456789012"
 }
}

Headers include:

Authorization: Bearer {token}
Traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01

The initial call span exists, but no child span appears for the transfer event. Is Genesys Cloud stripping the W3C context headers during the state change? I’ve tried injecting it into the custom attributes too, but that feels like a hack. Wondering if there’s a specific SDK method or header format I’m missing to keep the trace alive through the queue switch.