Flow-refs with expression are missing parent context

[manikmagar]

When a flow/subflow from an imported mule configuration are invoked, the span of the target flow is not connected to the parent context. The target flow's span appears as a root trace instead of a child of the main calling flow.

[manikmagar]

After a test for a given scenario, it was observed that Imported sub-flows or flows create correct spans and traces.

The issue was when the target flow was invoked using an expression -

<set-variable variableName="targetFlow" value="simple-subflow-logger"/>
<flow-ref name="#[vars.targetFlow]"/>

In this case, irrespective of where simple-subflow-logger exists (imported config or local config), the spans fromsimple-subflow-logger were getting attributed to root trace instead of under the simple-subflow-logger span.

I am renaming the issue to represent the finding.