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]

Hey @Thinzar,

First of all can I ask why you created Flows to do this instead of just patching directly with Power apps?

Since you display the data from Dataverse in galleries I assume that your App is connected to the Dataverse right?

What is The errorcode that comes back?

[Thinzar]

Thank you for your response, @DBO_DV .

I have connected the app with dataverse. 

Since the flow for storing the data from apps to dataverse table is not that simple, so I have to use the power automate flow.

You can also see that the data have to be passed to the automate flow in loop.

There is no error code. When the button is clicked, the included codes are run from the start to the end. But the two data storing automate flows are failed at the first try.

When I check the flow and run the previous failed flow automatically via the power automate flow, it works successfully.

[DBO_DV]

You can use the Patch function and a loop in front of the patch function to get exactly the same result. It would also be  a loop.

Patch(TableName,Defaults(TableName),{ColumnName:Data});
If(CountRows(TableName2)>0,ClearCollect(colTableName2);
    ForAll(colTableName2, Patch(TableName2,Defaults(TableName2),{ColumnName:Data})));
If(CountRows(TableName3)>0,ClearCollect(colTableName3);
    ForAll(colTableName3, Patch(TableName3,Defaults(TableName3),{ColumnName:Data})));

What is the error code inside of the Flow. You mentioned that they failed, so there has to be an error code.

[Thinzar]

@DBO_DV ,

They only shows like this and I could not view the error code. When I test that failed flow again in the power automate, the flow works successfully. Thats why.

[DBO_DV]

If you go here on Power automate 

 Select your flow and under details you can find the runs as well: 

You can select one of the failed runs to see what wen't wrong.

[Thinzar]

Thanks. 

This is the error message. 

In the flow, I have added the primary key name to the table as a foreign key.

Along with this, how should I add like this by using Patch you provided?

[Thinzar]

I think the flow ran first before creating the row in the primary table. Would this be the cause of error?

@DBO_DV 

[DBO_DV]

Yes this can cause the Error. But this is rather a Question for the Power automate Community.
If this is the problem However you can solve it by using a delay action. 

[Thinzar]

Thanks for your advice, @DBO_DV .

Is there any option for delay in power apps since it would be more convenient for me using delay in power apps than in automate flows.