Open edouard-chevalier opened 1 year ago
Both of these features (cascading terminate of sub-orchestrations and aborting activities) are currently on our roadmap to implement in the next 6 months or so.
In the meantime, I think the best you can do for aborting activities is to create a background thread that polls for the status of the parent. If the background thread discovers that the parent orchestration was terminated, abort the current activity execution (using a cancellation token, or whatever is appropriate for your scenario). We're likely to implement something similar to this in the framework down the road.
Hello, we have the current setup of orchestration and activities:
With
TaskHubClient
we can start the orchestration, and we want to be able to abort it, currently, we "terminate" the orchestration:The ADTF framework will indeed terminate the orchestration, but the task activity are still on going. These activities are pretty long to execute and, unfortunately, we cannot divide them in smaller activities. But they can take a
cancellationToken
.Is there any recommendation on how to implement cancellation of activities ? Bonus question: any recommendation on how to ensure that a sub-orchestration is also cancelled/terminated if the parent orchestration is terminated ?