I have a parent orchestration which calls multiple sub-orchestrations (it's a user interaction flow with multiple steps).
In my case, I wanted a want to simply terminate the sub-orchestrations that were in mid step waiting for user responses. I tried and it threw exceptions.
The solution was to terminate the parent orchestration first, then terminate any running or pending sub-orchestrations.
At that point, the exceptions stopped and I just ended up with warnings in the logs, which was fine.
This might be good addition to the docs.
HTH
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 6c17b738-aa32-4cbb-3d82-bda2bc032487
Version Independent ID: a34e246c-7c65-461f-4417-3c47eb4672e2
I have a parent orchestration which calls multiple sub-orchestrations (it's a user interaction flow with multiple steps).
In my case, I wanted a want to simply terminate the sub-orchestrations that were in mid step waiting for user responses. I tried and it threw exceptions.
The solution was to terminate the
parent
orchestration first, then terminate any running or pending sub-orchestrations.At that point, the exceptions stopped and I just ended up with warnings in the logs, which was fine.
This might be good addition to the docs.
HTH
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.