web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id : Rs6e8PB0s4avzlSe/LdG65
Power Automate - Using Flows
Unanswered

copying a flow breaks the original

Like (0) ShareShare
ReportReport
Posted on 20 Feb 2020 16:24:09 by 486

I have a flow that is triggered manually (button) the button takes inputs 4 inputs 2 boolean and 2 texts. when i copy this flow with "save as", the copied flow and the original is now missing the trigger inputs. 

the screenshot you will ask forthe screenshot you will ask for

 

 

Update: 
Concurrency settings is likely the source. 

 

Noticed that the same behavior when changing concurrency/settings of the trigger. Everything looks fine after selecting to save, exiting and returning to the editor show that the input fields are wiped. I can imagine the copy-process triggers the concurrency edit on the source as well as the one its copying, and that this process is not able to retain the input values. 


EDIT: 
Why is this marked as solved?

  • hjaf Profile Picture
    486 on 20 Feb 2020 at 17:15:04
    Re: copying a flow breaks the original

    Not sure, but i tested it again and now both the original and the copy are fine. 

    I think its not the copying that is the problem after all, i just noticed that simply opening the settings pane doing a change to anything breaks the inputs, but the trigger looks the same in the editor. except that the code for the inputs is gone.
    I believe I did this before I copied, and I thought that the trigger was fine because it did look normal before I saved and closed. 

     

    EditingEditingsettings, add a space to tracking id and remove it to click "OK"settings, add a space to tracking id and remove it to click "OK"code for inputs are gone.code for inputs are gone.

  • hjaf Profile Picture
    486 on 20 Feb 2020 at 16:58:11
    Re: copying a flow breaks the original

    No I have not attempted that, but i can't imagine it working because peek code also shows that the values are gone. As far as I know, the export import will use the code to create a new one.

    I guess I could copy that way as a workaround, but I still see the copy to/save as functionality to be broken 🙂 

  • yeinerlop Profile Picture
    on 20 Feb 2020 at 16:52:53
    Re: copying a flow breaks the original

    Hello @hjaf Could please try exporting the flow and then import it

     

    Please click and accept as Solution if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a Thumbs Up

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 2

Featured topics

Restore a deleted flow
Loading complete