System Nexus operations can select serialization context from the generated public request. For example, signal-with-start targets a different workflow ID than its caller.
The Worker-side reserved-endpoint path currently wraps the caller workflow payload converter in _SystemNexusPayloadConverter. It does not retain or rederive the operation-derived context for nested payload codec/external-storage processing after the outer envelope leaves the workflow sandbox.
As a result, codecs can observe the caller workflow context instead of the operation target context.
Expected behavior: retain the generated operation-derived SerializationContext when scheduling the operation and apply it to Worker-side nested payload and failure processing for that command and its completion.
Related cross-SDK work: TypeScript is implementing operation-context retention; .NET has a separate context-retention gap.
System Nexus operations can select serialization context from the generated public request. For example, signal-with-start targets a different workflow ID than its caller.
The Worker-side reserved-endpoint path currently wraps the caller workflow payload converter in
_SystemNexusPayloadConverter. It does not retain or rederive the operation-derived context for nested payload codec/external-storage processing after the outer envelope leaves the workflow sandbox.As a result, codecs can observe the caller workflow context instead of the operation target context.
Expected behavior: retain the generated operation-derived
SerializationContextwhen scheduling the operation and apply it to Worker-side nested payload and failure processing for that command and its completion.Related cross-SDK work: TypeScript is implementing operation-context retention; .NET has a separate context-retention gap.