As I often do that and have never had an issue in a server action I think they must be sequential unlike app connect which needs dependent actions to be run from the initial connections success event to ensure they run sequentially. Then again the solution may reside with workflow in app connect now, not had a chance to play yet.
@TomD, you have neatly brought me on to exactly the next question I wanted to ask:
My question is actually:
Do multiple Server Connect actions execute sequentially within one of the new Flows?
Or can we do a kind of "on Success" test in a Flow like we can do within the Dynamic Events area of a Server Connect?
I will use many flows to execute Server Connects and then do other things using the data I have just retrieved...