Orchestrations should be able to create sub-orchestrations, as described here. The Retry and error handling should work the same as the APIs for invoking activities.
One or more integration tests should also be written to exercise the sub-orchestration codepath.
Implementation notes
In addition to adding new public methods on the TaskOrchestrationContext interface, these lines of code need to be uncommented and fully implemented in order to handle history events associated with sub-orchestrations.
Requirement
Orchestrations should be able to create sub-orchestrations, as described here. The Retry and error handling should work the same as the APIs for invoking activities.
One or more integration tests should also be written to exercise the sub-orchestration codepath.
Implementation notes
In addition to adding new public methods on the
TaskOrchestrationContextinterface, these lines of code need to be uncommented and fully implemented in order to handle history events associated with sub-orchestrations.When writing the integration test, this .NET Isolated sub-orchestration test can be used as a reference.