Tests are ALWAYS running in parallel despite setting a flowsOrder configuration

[joshuadeguzman]

Describe the bug Tests are always running in parallel despite setting the flowsOrder, which is a bit confusing because this doc clearly outlines that other tests should run right after Flow A, without adding them explicitly in flowsOrder.

What happens is that, the rest of the flows not added explicitly, and in order in flowsOrder are opening the app in a logged out state. Flow A represents a login existing user flow in our project.

To Reproduce

1. Set the executionOrder to:

executionOrder:
  continueOnFailure: false
  flowsOrder:
    - Flow A

2. Run maestro cloud

Expected behavior

• Flow A should run first before everything else

Environment information (please complete the following information):

• Maestro version: 1.35.0
• Platform: Maestro Cloud
• Framework: Flutter
• Device model and OS version: Android

Workspace (if applicable) You can browse our files here, needs authentication.