Flow options

[Wibbly]

If I set a flow option to "Wait until the currently executing instance has finished", what does this do?

Does it postpone a second instance of the same flow starting to execute until the current one finishes or fails? If so how many instances can be "waiting/postponed" at once?

Use case is a flow that triggers taking photos etc. on a single failed login. Login might be attempted up to 5 times before the OS enforces a 30s wait, but the flow takes a while to execute. Using "Wait until the currently executing instance has finished", will the flow be executed 5 times (eventually)?

[Martin]

Yes, "Wait until the currently executing instance has finished" waits as long as the currently executing instance still runs.

I recommend to create a test flow to see how each execution policy works:
-trigger <none>
-action Sleep: 1s
-action Sleep: 1s
-action Sleep: 1s
-action Sleep: 1s
-action Sleep: 1s
-action Vibrate

Set the flow execution policy to "Wait until the currently executing instance has finished" and use menu->Execute to start the flow a few times. The number of waiting instances should be shown on the upper right side of the trigger.

[Wibbly]

Thanks. It worked with 9 instances pending. Good enough for me