cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

WaitUntil and Sleep functions

Submitted by Anonymous on ‎06-13-2018 11:36 AM

Ideas

  • WaitUntil function which accepts a boolean (true or false) value as the parameter and causes the app to wait until that boolean value is true
    • Example - Waiting until a patch is complete to navigate to a different screen
  • Sleep function which takes a time in milliseconds as the parameter and causes the app to sleep for that specified time

These two functions would be very helpful in a variety of situations and I believe they would positively impact the flow of my applications. 

Status: New
5 Comments (5 New)
Comments
Gargoolgala
Resolver II
Resolver II
‎06-21-2018 08:39 PM

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.  

RusselThomas
Microsoft
Microsoft
‎07-18-2019 05:33 AM

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!

PaulD1
Super User
Super User
‎12-11-2019 08:46 PM

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.

ArjenHofland
Regular Visitor
‎05-30-2020 01:29 AM

Wait untill is basically a need to have if you want to keep your code neat and always working properly in certain scenario's.

 

I for one, would be ever so thankfull for this. For the timer only works if the request is acually handled within that particular timeframe. If for whatever reason it takes longer, the logic fails. 

PaulD1
Super User
Super User
‎06-25-2020 01:43 AM

In the specific case of waiting for a Patch to complete, I think you may be able to force that by assigning the output of a the Patch to a variable - something like:

UpdateContext({conPatchID:
Patch(tblPatchTable, Defaults(tblPatchTable),{Column1: "My Value"})
);
If(conPatchID.ID > 0, Navigate(NextScreen,Fade)

This is a bit of a hack though and no guarantee that the behaviour of such a construct won't be changed in the future.

There are many other times when you want a specific command/set of commands to complete (say, loading a dataset into a local collection) before moving onto the next command so having a Wait command that you could wrap around multiple statements (like Concurrent) would be a great addition.