I have a script that has a multiple actions with one controlling action and several supporting actions. When I run the script the control action executes making the calls the support actions then it runs the supporting actions again. It appears to be running all the actions in sequential order starting with the control action and going through all the other actions. I have been trying to figure why this is happening but I haven't had any success so I am hoping that it is a configuration issue and I just don't know what to look for. I would appreciate any ideas for an resolution or workaround.
Nevermind, I figured out what the issue was. It was related to an option that I selected when I created the action. So, when creating an action you select where to place the call to it. The options are "At the end of the test" or "After the current step" and if you select the first option then the call get inserted in the test-flow which means that the action is not nested. However, if you select the second option then the call is inserted after the current step in the current action therefore making the action nested. To resolve the issue I had to create a new action with the correct option selected to insert the call the after the current step and copy my code from the old action to the new one. When I ran my script again it worked as I expected it to. I hope this can help someone else.