Can we increase the 2 minute timeout when calling a flow from power apps

[johnjohnPter]

I am calling a power automate flow from power apps, sometimes the workflow takes more than 2 minutes, which is causing the call to fail due to time out.. is there a way to increase this 2 minutes timeout?

The power apps send 2 parameters >> then the power automate flow loop through all the planner plans and return a list of Planner tasks which are assigned to the user based on the passed parameters. then i am getting the data from the flow and populate a gallery inside my canvas app..

Thanks

[johnjohnPter]

@SennyT2101 i need to get all the Tasks that have specific status (not started, completed, inprogress or all of them) from all the plans that are under all the groups.. not sure if i can do this directly inside power apps?

here are the main flow tasks:-

and the details of the tasks:-

[AmDev]

Yes, you can do this directly in Power Apps. The below example is where I have just brought in all my tasks (those created by me)

I have then used AddColumns to surface the '_assignments' UserId (under the new 'assignmentTxt' column) - this could then be used to filter by the app user or a selected user in the app. You will need to use the 365Users connector to grab the UserId you want to filter by.

If you want to grab tasks from all groups / plans that were created by anyone, that may require the need to use the Office 365 Groups connector to list the groups and then use that list (with a ForAll) to loop through and grab the tasks for each plan, and then do you status filter.

Essentially the same as what you have done in Power Automate, but in Power Apps, which splits the API calls up and (should) ensure you stay well below the 2min threshold.

Hope this helps

[johnjohnPter]

@AmDev ok will try this, but i do not necessary want the Tasks assigned to me, i have a comboBox to select any user and a comboBox box to select the status , then i wanted to get the related tasks..

[IAmIntractable]

Split your flows into smaller chunks and call in succession. If you are changing these embedded flows outside of the App Maker be sure that you refresh the flow in the App Maker and republish. There have been issues on the platform of late. I have an embedded flow that runs sub second...but some of the runs went on for 6 minutes...the app stopped waiting after 2 minutes. There is NO valid reason for this to occur.