These two functions would be very helpful in a variety of situations and I believe they would positively impact the flow of my applications.
Hi, whle I agree a wait/sleep option would be ideal the way I get around this is to create a timer and then action the item I need doing next on the TimerEnd option.
This works for the sleep option but not wait as you have to experiment until you ge tthe timer duration right.
Timer option doesn't help within a ForAll - I'm hitting API quota limits (submissions per second) - would be handy to have it wait even 1 second before processing the next record.
Right now I'm farming off a request to flow which responds after a 1 second wait time - what a waste of flow quota!
Ability to force PowerApps to wait for a process to complete before contuing to the next command would be great. My suspicion is that asynchronous behaviour can change somewhat from version to version so to be able to confidently force PowerApps to wait for a Patch to complete (for example) before changing screen / refreshing / whatever would be welcome.