Trying to consolidate some logic across three inbound voice flows. Instead of duplicating the same Data Action calls for CRM lookups, I want to call a single ‘Common’ flow from each entry point.
The goal is to keep the OpenTelemetry span context intact while passing the interaction ID. I’m using the POST /api/v2/flows/executions endpoint to trigger the shared flow. Here is the payload structure I’m testing:
{
"flowName": "common_crm_lookup",
"execution": {
"interactionId": "{{interaction.id}}",
"triggerSource": "inbound_call"
}
}
The issue is that the span context seems to get lost or duplicated when the new flow execution starts. The parent span in Jaeger shows the initial trigger, but the child spans from the Data Actions inside common_crm_lookup appear as root spans rather than being linked to the original call trace.
I’ve tried injecting the traceparent header into the execution payload, but the endpoint ignores it. Is there a specific way to pass the context ID so the backend service can reconstruct the trace? Or am I approaching this wrong?