Repository navigation
Description
Describe the feature
Add a SubType property to StepConfig and CallbackConfig in Amazon.Lambda.DurableExecution, as ChildContextConfig.SubType already has.
Today StepOperation always sends OperationSubTypes.Step, and CallbackOperation always sends OperationSubTypes.Callback. Neither config class has a way to change that.
Use Case
- A function can compose several durable operations into one larger operation.
ChildContextConfig.SubTypelets such a function label its child context, for example"OrderSaga".- The steps and callbacks inside that context cannot be labelled. They always record
SteporCallback. - So execution history and plugins can tell those parts apart only by parsing their names.
The JS SDK added the same options in aws/aws-durable-execution-sdk-js#939: StepConfig.subType and CreateCallbackConfig.subType. Issues for the other SDKs: aws/aws-durable-execution-sdk-go#104, aws/aws-durable-execution-sdk-java#757, aws/aws-durable-execution-sdk-python#749, aws/aws-durable-execution-sdk-rust#73.
Proposed Solution
- Add
public string? SubType { get; set; }toStepConfigandCallbackConfig. - In
StepOperationandCallbackOperation, sendconfig?.SubTypewhen it is set, and the current default otherwise. That covers every checkpoint update: START, SUCCEED, FAIL, and RETRY for steps, and START for callbacks. - Validate the value before the operation is created, for the new properties and for
ChildContextConfig.SubType:nullor an empty string selects the default.- The service accepts 1 to 32 characters from
[a-zA-Z0-9-_]. It rejects any other subtype with HTTP 400ValidationException, and rejects the whole checkpoint request. So the SDK should throw a clear configuration error first. TodayChildContextConfig.SubTypeis sent unchecked.
- Optionally, make
InMemoryDurableServiceClientinAmazon.Lambda.DurableExecution.Testingreject an invalid subtype with the service's message. For example:1 validation error detected: Value 'bad subtype!' at 'updates.1.member.subType' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z0-9-_]+. The JS testing SDK does this since feat(sdk): add subType to step and createCallback aws-durable-execution-sdk-js#939.
Two details to keep:
CheckpointProcessorin the testing package applies WaitForCondition-specific handling whenSubType == OperationSubTypes.WaitForCondition. A step with a custom subtype does not match, so it keeps plain-step handling. That is the right behavior, becauseWaitForConditionsets its own subtype and gets no option.ValidateReplayConsistencycompares the operation type and name, but not the subtype. The other SDKs also compare the subtype. If .NET adds that check, changing a subtype becomes a breaking change for executions in flight, and the property's XML doc should say so.
Other Information
No behavior changes without the new properties. The SDK records the same subtypes as today.
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
AWS .NET SDK and/or Package version used
Amazon.Lambda.DurableExecution 2.1.0 (source at master, c504691)
Targeted .NET Platform
All supported targets.
Operating System and version
Not applicable.
Activity
github-actions commentedon Oct 7, 2026
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.