Power Automate flow stuck on “Run an agent” action when using a Fabric Data Agent

(0) Share

Report

Posted on by AG-22071503-0

My Power Automate flow works as expected until it reaches the Run an agent action. The Copilot Studio agent used by this action is connected to a Fabric Data Agent.

In Copilot Studio, the Activity pane shows that the agent successfully completed its task. However, the flow never receives a response or return value. As a result, the flow remains in a running state and does not proceed beyond the Run an agent action.

Is there a configuration change or workaround in Power Automate, Copilot Studio, or Microsoft Fabric that will ensure the agent’s response is returned to the flow so that execution can continue?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
This behavior isn't expected. If the agent has completed successfully in Copilot Studio, the Run an agent action should receive the response and continue the flow. If it remains in a running state, try the following checks:

Verify the Fabric Data Agent is published and that the latest published version is connected to the Copilot Studio agent.

Confirm the Copilot Studio agent is also published after any recent changes.

Test the same prompt directly in the Copilot Studio Test chat. If it also hangs there, the issue is likely with the agent or Fabric rather than Power Automate.

Try a very simple prompt (for example, "Hello" or a query that returns a small result set) to rule out long-running queries or large responses.

Ensure the Power Automate, Copilot Studio, and Fabric resources are in the same tenant/environment and that the connection used by the flow is valid.

Recreate the Run an agent action (or the connection reference) in a new test flow to rule out a stale connector configuration.

If the agent uses Microsoft Fabric data sources, verify the calling identity has access to the Fabric workspace and underlying data.

Check the Flow run history and Copilot Studio conversation/activity logs for any correlation IDs or hidden errors that can be provided to Microsoft Support.

If the issue persists after these checks and the agent consistently completes in Copilot Studio while the flow never receives a response, it is likely a product issue or preview limitation. At that point, collecting the Flow Run ID, Copilot Studio conversation/activity ID, environment ID, and timestamp before opening a Microsoft support ticket would help engineering investigate.

Was this reply helpful? Yes No
SS-14071457-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Ashlesha-MSFT im also having the same issue : I’m building a weekly VoC report in Copilot Studio where the agent generates the report from HubSpot feedback and notes, plus reviews, and meeting evidence, but the flow gets stuck on the Run an agent step and stays running for a very long time. In my tests, it did not complete in a reasonable time and never returned a clean timeout, which makes the automation unreliable for a scheduled weekly report.
I expected the agent to either finish within the supported runtime or fail clearly, but instead the flow appears to hang during the agent handoff. This blocks production use for a report that needs to be generated and emailed automatically every week, and it seems to point to a latency or timeout handling issue in the synchronous agent flow pattern.

Was this reply helpful? Yes No