Sending a quick reply card via POST /api/v2/conversations/messaging/messages works fine, but the trace context drops. I’m injecting the W3C Traceparent header in the request, yet the downstream Data Action span shows no parent ID.
{ "content": [{ "type": "card", "body": ... }], "traceparent": "00-..." }
Jaeger shows two separate traces. Is the Genesys Cloud API stripping custom headers before processing the message?