Thanks Emilio. It is working in general.
However, when I execute the ExerciseSpace-Kurt > Part 5b - Orchestration > 02.Feedback_Analyzer workflow I get “Finished successfully” with the following error:
ERROR Call Workflow Service 3:402: Execution failed in Try-Catch block: Failure, workflow was not executed, current state is IDLE. Call Workflow Service 4:2404: Execute failed: 422 Execution context ‘aa82b2ec-ce1f-4cae-877b-a6a71e92d067’ is not available for space ‘*eXlU_LH9xBhBhDDl’: Execution context ‘aa82b2ec-ce1f-4cae-877b-a6a71e92d067’ not found
I opened all the workflows and checked that the callee wf can be found which is the case. So I do not know what produces this issue.
This issue looks similar to what has been reported above by @ajackson .
The error is thrown when a Call Workflow Service is configured to use an execution context that is not available. If that’s the case, you need to open the configuration of the node so that it detects the available execution contexts. Next to the instructions, there is a red annotation with the detailed instructions to troubleshoot this issue.
For this exercise, however, finding the failing node is not obvious because it is in a nested call. I have updated the exercises to remove the nested call, now it should be easier to find all the Call Workflow Service nodes. If you have time it would be nice if you can
After long time, I realized that I must “disconnect” the “Data App Flowchart” before I can implement the configuration on the Column Selection Configuration nodes.
It took me the hell of a long time to realize that you have to right click on the node and click Configure, instead of clicking on the upper left Configure button. What’s the difference between the two? No idea…
