Power Platform Community Forum Thread Details

Hello,

We are experiencing a consistent bug in Microsoft Copilot Studio when trying to publish flows that contain a "Run an agent" action.

**Environment:** Microsoft 365 / Power Platform (Commercial, Production)

**Error Message:**

Flow server error returned with status code "BadGateway" and details "DynamicSchemaResponseNotSchema"

**Steps to Reproduce:**

1. Create a flow in Copilot Studio Designer

2. Add any action (e.g., HTTP request, Send an email, etc.)

3. Add a "Run an agent" action step

4. Click the "Publish" button

**Expected Behavior:**

The flow should publish successfully.

**Actual Behavior:**

Publishing fails immediately with the error: "Flow server error returned with status code 'BadGateway' and details 'DynamicSchemaResponseNotSchema'"

**Key Observation:**

- This error ONLY occurs when the flow contains a "Run an agent" action step.

- When we remove the "Run an agent" action from the flow, publishing works perfectly with no errors.

- We have 4 different flows affected by this issue, all containing "Run an agent" steps.

**Affected Flows:**

We have 4 flows in our environment that are affected by this issue. All of them share a common structure that includes a "Run an agent" action step (e.g., Manually trigger → HTTP → Run an agent → Send an email).

**Impact:**

We are completely unable to publish any flow that uses the "Run an agent" action, which is a core feature of Copilot Studio. This is blocking our production workflows.

Please investigate this issue. It appears to be a server-side bug related to how the "Run an agent" action's dynamic schema response is validated during the publish process.

Thank you.

Categories:

Bot extensibility

@OM-20040602-0

From what you’ve described, particularly that the issue occurs consistently only when you add the “Run an agent” action to your flow, it appears to be more of a platform/service issue (Copilot Studio) than a flow configuration issue.

As it's impacting multiple flows and is preventing publishing in a production environment, I would recommend raising a Microsoft Support ticket .

The Microsoft Support team will have access to backend logs and be able to further analyze the DynamicSchemaResponseNotSchema error, which we, as clients, do not have access to view.

The Microsoft Support team will also be able to verify whether this is an existing product-related issue or a bug needing to be resolved by the product team.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥