What you’re doing here is launching several scenarios, and scenarios won’t be launched sequentially, they’ll all start when the simulation starts.
Of course, you can delay some scenarios using nothingFor(…) to make sure they won’t start at the exact same time.
However, all is not lost, there is a way to start Gatling simulations sequentially.
Gatling’s SBT plugin (https://github.com/gatling/gatling-sbt) is able to find all the simulations defined in a SBT project’s test sources and, using the “gatling:test” command, will run all those simulations sequentially.
Would a workaround for running sequentially not be to define unique simulations including the main one and run them using a shell script starting gatling “non interactively”?