That makes sense, thanks.
To clarify the use case, we have a long running workflow where API requests will in turn result in signals into the workflow. Currently the workflow will have a single trace with a trace id that is propagated to it from the initial API request to start it. What we were considering was for each signal to pass in the trace id, so that workflow actions taken after that signal would be associated with the trace id passed in by the signal.