TaskHubClient.CreateOrchestrationInstanceAsync() called within an orchestration seems to hang
See original GitHub issueHi,
So, I’ll explain my scenario. I have an orchestration (let’s call it ValidationOrchestration
) that does some validations based on an event received on the service bus (my application sends a request event on the service bus for another application and is expecting a response at some point in time). If the validations pass, I create another type of orchestration (let’s call it ProcessingOrchestration
) using TaskClient.CreateOrchestrationInstanceAsync()
. I am doing this because I want to seperate the validation code from the processing code. I thought it would work but it seems that the ValidationOrchestration
instance is waiting on the ProcessingOrchestration
it started to complete. I would be expecting this behaviour with CreateSubOrchestrationInstance
. I want the ValidationOrchestration
to start the ProcessingOrchestration
and then complete. Did I do it right?
Thank you
Issue Analytics
- State:
- Created 6 years ago
- Comments:8
Top GitHub Comments
@cgillum So, to give you a feedback, I used a
TaskActivity
to wrap my call toCreateOrchestrationInstanceAsync()
as you suggested and it worked. Thanks again for your help.It is clearer now. Thanks a lot for the detailed explanation.