Power Platform Community Forum Thread Details

Sure. Here's a generalized bug report that doesn't reference your specific flow, tenant, site, or project.

Power Automate Bug Report

Title: Save As appears to succeed but does not create a copied cloud flow

Product:
Microsoft Power Automate (Web)

Issue Summary:
Using the Save As function on an existing cloud flow appears to complete successfully, but no copied flow is created.

Steps to Reproduce:

Open an existing cloud flow.

Select Save As.

Enter a new flow name.

Select Save.

Wait for the operation to complete.

Expected Result:

A new cloud flow is created using the specified name.

The copied flow appears in the flow list.

The user receives a success confirmation message.

Actual Result:

A progress indicator briefly appears and then disappears.

No confirmation message is displayed.

The user remains on the original flow.

The newly named flow does not appear in the flow list.

Refreshing the page does not consistently reveal a copied flow.

No error message is presented to the user.

Impact:

Users are unable to reliably duplicate existing flows for reuse.

Creating similar flows requires manual reconstruction and increases the risk of configuration errors.

Lack of a success or failure message makes troubleshooting difficult.

Additional Notes:

The original flow remains functional and editable.

The behavior occurs without any visible validation or permission errors.

The issue appears to be intermittent because the copied flow may briefly appear in the user interface and then disappear after refresh.

Suggested Improvement:
The Save As operation should provide clear success/failure notifications and either:

Automatically open the newly created flow, or

Navigate directly to the copied flow's details page after creation.

This would eliminate ambiguity regarding whether the copy operation completed successfully.

Categories:

Building flows

Before filing this as a product bug,

worth ruling out two environment-scoped causes, because I tried the same repro today on a non-solution cloud flow and Save As behaved normally , which points to environment or account scope rather than a platform-wide regression.

1. Check where the copy actually landed. Save As on a solution-aware cloud flow creates the copy inside the solution the original lives in, not in My flows > Cloud flows. If you ran Save As from a solution flow and then looked in My flows, you'd see exactly what you're describing.

Copies are also created in a turned-off state, so any list view filtered on status will hide them. And confirm the environment picker didn't shift, the copy goes to the environment that served the request, not necessarily the one you're now browsing.

Reference: Save a copy of a solution-aware cloud flow into a solution , learn.microsoft.com/power-platform-release-plan/2022wave2/power-automate/save-copy-solution-aware-cloud-into-solution

2. Confirm you hold Environment Maker in that environment. Save As is a create operation, not an edit. If you were made co-owner of the original flow but don't have Environment Maker (or the Dataverse create privilege on Process in a Dataverse-backed environment), you can edit the original all day but the create call fails. The designer doesn't surface that 403, you get a spinner and nothing else, which matches your Actual Result line for line.

Reference: Guide to cloud flow sharing and permissions : learn.microsoft.com/power-automate/guide-to-cloud-flow-sharing-permissions
To get the actual error: open F12 > Network before clicking Save, filter on flow.microsoft.com, then run Save As. Look at the POST that fires when you confirm the name. The status code and response body are the error message that never reached the UI, and the response carries a correlation ID. That's the single most useful thing to attach if you do open a support ticket.

Two smaller things I've hit in production: very large flow definitions can have the Save As call time out with no UI feedback, and premium connectors in the source flow will fail the create if the copy can't be license-validated. DLP is less likely to be your cause , a DLP conflict still creates the flow and marks it Suspended rather than producing nothing.

Workaround in the meantime: Export (Legacy) > Import, or Send a copy. Both take different code paths from Save As.