@weezo. Having looked at your flow, I have 3 comments:
1. It looks like every separate "thread" in your flow ends with "Stop flow". I did the same for the first couple of weeks using Automagic, until I discovered that it was unnecessary - a flow will automatically stop when it has reached the end of all of its component threads. So, now, most of my flows don't have a "stop flow" action - I use it only in specific circumstances (which I won't detail here). So far as I can tell, you could remove all of those terminal Stop flow actions, and your flow would still work.
2. Why may the above be relevant to the issues you've had? You've mentioned having to increase sleep to 16s, because the flow didn't work when sleeps were set at 7s. I wonder if, when set at 7s, one of the threads was reaching its "Stop flow" action when another thread was still active - in which case, that second thread wouldn't be able to run to completion - it'd be stopped mid-stream. If this hypothesis is correct, then removing all of the terminal "Stop flows" might actually improve things, because all threads would be allowed to complete. You also may be able to reduce the duration of your sleeps, making the flow more user-friendly.
3. Again, this is something that I realized only after using AM for a couple of weeks. Maybe you know already this, but if not: you can visualize the flow as it runs. This can help to determine where a problem lies. To do this, open the flow (as if you were going to edit it) and then tap the menu icon, and tap Execute. You'll see the flow "in action", represented by red boxes / lines.
Help with input dialogue
Moderator: Martin
Re: Help with input dialogue
@Scotty. Thank you for that input. I am new to AM and dont know the intricacies of it. I will try your suggestion and see how things work out. Thank you!