Injecting OTel context into Genesys Common Module calls

What’s the right way to keep my OpenTelemetry trace when calling a shared Common Module from multiple inbound flows? I need the downstream Data Actions to pick up the parent span.

  • Using Architect Common Modules for shared logic.
  • Injecting traceparent header via a Data Action before the call.
  • Context drops at the module boundary.
  • No code errors, just silent trace loss.

How do I pass the context through the module invocation?