We are running into a problem capturing accurate tracing information in our logs during API calls that trigger signals inside a workflow. We found that Signals do not support Context Propagation the way that starting the workflow does. We have a similar intended case to another support issue that was raised here: Context propagation on signals in go - #4 by robryan where we want the tracing propagated through from an API call that sends the workflow signal so we can fully track the actions within that same trace. There is a suggested path to pass trace information into the signal payload, but we are then limited by the workflow.Context type to actually be able to update the trace id in context being used by open telemetry.
It looks like there is no work-around solution provided on that post so we are looking for any additional help that would allow us to customize our use of Signals to support this, or any info on potential changes to this capability in the future.