Answered

Copilot Studio Flow designer seems broken

(0) Share

Report

Posted on by HH-23060802-0

Since yesterday or the day before Copilot Studio Flow designer seems broken.
When clicking Save draft or Publish the UI refreshes and changes seems lost.
When going to Copilot Studio Flow overview you can see that at every Save draft or Publish a new Copilot Studio Flow is generated with exact same name as the original, but with a new endpoint meaning anything calling the Copilot Studio Flow will still call the old version.
This must be a bug.
No fitting Categories found.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Assisted by AI

Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @HH-23060802-0,

This sounds like a platform synchronization bug rather than expected behavior.

In Copilot Studio, flow editing should follow a standard draft-to-publish lifecycle. When saving or publishing spins up a brand-new flow instance with a different endpoint instead of updating the existing one, it indicates a solution synchronization disconnect between the Copilot Studio canvas and the Power Automate backend.

Because the integrated Power Automate designer pane runs inside the Copilot Studio wrapper, state-tracking failures can cause the interface to lose track of the original flow's unique GUID and generate duplicates.

A few workarounds to bypass this right now:
Edit Directly in Power Automate: Open your environment's Solution portal directly in the Power Automate maker portal and edit the flow there. Saving it within its native environment forces a direct update to the existing GUID, completely bypassing the Copilot Studio save wrapper.

Track Flow GUIDs: Note the unique IDs in the browser URL bar when editing to document exactly when the duplication behavior triggers.
Clean up Orphans: Manually delete the duplicate cloud flows created in the background solution so they do not cause downstream environment clutter or trigger conflicts.

If editing natively in Power Automate does not resolve it, I recommend opening a Microsoft support ticket. This behavior points to an environment-level solution regression rather than a configuration error on your end.

✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/

Was this reply helpful? Yes No
HH-23060802-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Sunil Kumar Pashikanti

I am not able to see any of my Copilot Studio Flows in make.powerautomate.com or in PPAC.
That was also the case before the synchronization bug started.

Was this reply helpful? Yes No
Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

We validated the flow lifecycle in our tenant and couldn’t reproduce duplicate-flow creation. To investigate your case properly, please raise a support ticket and share tenant/environment details plus logs (HAR, console, timestamps, flow IDs/endpoints). Once support captures backend traces, we will escalate to engineering immediately if a platform issue is confirmed.

Was this reply helpful? Yes No
HH-23060802-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Sunil Kumar Pashikanti

I did the cleanup of copies left behind you suggested and yesterday I was able to save again without copies of the Flow being generated.

Was this reply helpful? Yes No