class NexusSerializationContext(SerializationContext): (source)
Serialization context for Nexus operation payloads.
Callers receive this context when encoding inputs and decoding results or failures. Handlers receive it when decoding inputs, encoding synchronous results, and encoding failures produced while handling a Nexus task.
Workflows and standalone activities started by a handler, and workflow updates it sends,
receive this context through the server and use it for payloads returned to the caller:
results, failures, and standalone activity heartbeat details. Clients decode these with the
context the server returns. See
temporalio.activity.Info.nexus_serialization_context for asynchronous completion.
A standalone operation handle decodes with the context the server returns, falling back to the context used to start the operation on older servers.
A failure encoded by a handler is later decoded by a caller. Because some operation paths may lack this context, contextual encodings must be self-describing and decoders must continue to accept payloads encoded without context.
Warning
This API is experimental and unstable.