Power Platform Community Forum Thread Details

Hello,

I am creating a Copilot Studio agent that calls a Power Automate flow which takes 5 minutes to run. The agent however gives a time out error and stops but the Power Automate flow succeeds after 5 minutes. Is there a suggested approach so that the agent does not stop execution early since the Power Automate flow succeeds? Thank you

Categories:

Autonomous agents

Hi @CU04022236-0,

Copilot Studio cannot wait 5 minutes for a synchronous Power Automate call. To avoid the timeout, trigger the flow asynchronously and let the agent respond immediately while the flow finishes in the background.

Copilot Studio waits synchronously for a Power Automate flow to return a result. During this wait, the agent cannot continue the conversation, and if the flow takes too long (like your 5‑minute flow), the agent will hit its timeout and stop, even though the flow eventually succeeds in the background. Microsoft documentation confirms that off‑agent operations such as Power Automate calls are synchronous and can lead to long waits or timeouts in the agent.

Either reduce the time of the workflow to run below <5 minute window (Optimize/shorten the flow) or trigger the flow asynchronously.

Asynchronous pattern
Trigger your Power Automate flow asynchronously (e.g., via a simple starter flow, queue message, or HTTP trigger).
Let the flow complete its long processing in the background.
Return control to the agent immediately so it doesn't timeout.
Deliver the flow’s final result through another channel (Teams, email, Dataverse update) or let the user return to the agent to check status.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.