only the first query ran and the remaining queries failed on the first execution in power apps

[Thinzar]

I have built an app linked with Dataverse. 

In the scenario, when the specific button is clicked, all three power automate flows written in power apps formula onSelect property of that button will have to be run normally and then all three kinds of data have to be stored in their associated Dataverse tables. 

The problem is that whenever the button is clicked for the first time after along time (like after a few hours), only the first flow among the existing three flows could be run successfully, and the remaining two flows failed. However, when I click the button for the second time, starting from the second time, all three flows are run successfully. 

All of the three flows are written to store the data from power apps inputs to each relevan Dataverse tables.

May I know which is causing that problem and how could I fix it or prevent it?

The related formulas and screen are attached below.

Thanks for all of your response.

[DBO_DV]

 @Thinzar , 

No there is no function in Power apps, since power apps function with the same trigger work in sequence. 

You could use something like this. 

If(... Set(varAnswer1,FlowName1.Run(...));
If(... Set(varAnswer2,FlowName2.Run(...));
If(... ,FlowName.Run(...);

When you always respond to powerapps and save the response into a Variable the next function waits on the variable to be set. 

but the for all Loop could really make it complicated

[Thinzar]

Thank you for the advice, @DBO_DV . Unfortunately, it does not work.

The problem still persists. Could there be any other way that could help it?

[DBO_DV]

Did you try using Delay inside the Flow?

[MuhammadAizaz1]

Hi @Thinzar ,

You can use Timer control to achieve this.

on button select type your first part of the code then initiate timer start. Then execute another part of the code in onTimerend property of the Timer.

Hope this resolves your issue.

[DBO_DV]

Hey @MuhammadAizaz1 ,

great idea this totally slipped my mind. 

@Thinzar if you need to keep it in Powerapps Muhammad's solution will probably work best. 

Keep in mind that you should not send two request directly after eachother with this solution since the timer will either setback or ignore the second call. 

It would also be best to stay on this site untill all requests are send. This is recomended so you den't get problems with your perfomance in the app. 

Otherwise try asking in the Power automate forum since they will be able to help you out much better with your flow. 

[Thinzar]

So, I have to use the Timer as a button instead of the button?

Could you please explain more in details or share the detailed explanation documents or videos for this?

Thank you for your help, @MuhammadAizaz1 @DBO_DV .

[DBO_DV · Accepted solution]

No the first part stays in your button: 

If(... FlowName1.Run(...);
UpdateContext({varStartTimer1:true})

The variable is used to have full control over the start of your timer.

in the OnTimerEnd Property of your timer you need to put this:

UpdateContext({varStartTimer1:false})
If(... FlowName2.Run(...);


//If you need a Second Timer add this:
UpdateContext({varStartTimer2:true})

If you need two timers because the third flow would need the second one to finish to work you just do this again with the other variable, flow and timer

in the AutoStart property of your timer put the variable

varStartTimer1

To test it you need to preview the app. By just pressing "ALT"+Clicking the timer wont start. They can only start in preview or when you really play the app. 

On Duration you can modify the duration in milliseconds. 

[Thinzar]

It works!!!!!

Thanks for your detailed illustration, @DBO_DV .

Along with this, I would like to clarify that, the flow and every formula written after the flow1 which starts the timer, will have to be written in the timer's onTimerEnd Property, right?

[MuhammadAizaz1]

Yes right @Thinzar