Unanswered

unable to edit flows after most recent update

(1) Share

Report

Posted on by AConnelly

When using Power Automate Desktop, we can no longer edit some of the pre-existing flows in the V1 schema after the latest update to Power Automate Desktop. The flows refuse to open and give the following message:

ERROR DURING FLOW INITIALIZATION

Flow initialization failed. Please make sure there is an active internet connection and contact your administrator.

How can we open and edit these flows? They are critical to our operation and there is nothing in support that we could find to address this issue.

Categories:

Power Automate Desktop

I have the same question (1)

All responses (12)

Answers (1)

Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (2)

Report

@AConnelly

Have you tried with disable the schema V2 and restart your PAD and see whether it allows to edit or take backup of your flows?

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
AConnelly 30 on at

Like (1)

Report

I have not, as I'm not certain how it was even enabled in the first place. Could you provide me the steps to disable schema V2 at least temporarily??

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (1)

Report

@AConnelly

Here you go!!

Open the Power Platform Admin Center, click on 'Environments', select your environment, navigate to 'Settings', and then to 'Features'. Scroll down to find the 'Enhanced desktop flow schema' where you can enable or disable the settings.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
AConnelly 30 on at

Like (1)

Report

Deenuji,

Thank you so much. Unfortunately, these features are grayed out and state:

"Enhanced schema has been enabled on your organization by Microsoft. To disable it, please contact the Support."

So I guess I'll have to reach out to Support somehow. I wonder why this was enabled in the first place? We never asked for this.

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (2)

Report

@AConnelly

I have pasted the below from Microsoft document:

v1 schema will be deprecated Soon:

Convert desktop flows stored in the v1 schema to the v2 schema by end of 2024, as then the v1 schema will be deprecated. You need Power Automate for desktop v2.29 or later to author and run desktop flows using environments where the v2 schema is enabled.

Please refer the below article for more details:
Power Automate v2 schema - Power Automate | Microsoft Learn

Another workaround is to navigate to the Processes Dataverse table, where you can view all the details of flows with schema versions and Power Automate Desktop workflow details. You can copy this code and make some alterations to ensure it functions correctly.

But note this option would require lot of efforts and patience to bring back your flows to work.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
AConnelly 30 on at

Like (1)

Report

Honestly, if you could just tell me what steps I need to take to migrate one of our desktop flows from the affected environment to another environment that doesn't have V2 enabled, that would help me.

Was this reply helpful? Yes No
AConnelly 30 on at

Like (1)

Report

Honestly, if you could just tell me what steps I need to take to migrate one of our desktop flows from the affected environment to another environment that doesn't have V2 enabled, that would help me.

Was this reply helpful? Yes No
Verified answer

Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (2)

Report

@AConnelly
Please navigate to the make.powerautomate.com website, select 'Solutions', and create a new solution. Then, proceed to establish all necessary desktop flows and generate a publisher profile. Following this, export your solution, download the resultant file, and import it into a different environment.

So in short if you have premium license for Power Automate? If so then best way is to use export/import.

Or you could just login to the same account in Power Automate Desktop in the different computer.

But if you need to move just the Power Automate Desktop flow and don't have premium license and cant use the same Power Automate account then you can just copy and paste the code.

1. Select all actions (Ctrl + A) and copy them (Ctrl + C)

2. Paste the code into text editor like notepad

3. Move the notepad file which has all the code to the new computer
4. Copy the code from the note pad (in the new computer)

5. Paste the code to the new PAD flow

Note that the Power Automate Desktops should be same versions in both computers (or atleast the one that you created the flow on shouldn't be newer version than where the flow is moved to). So remember to update the new computers PAD to newest version.

https://www.linkedin.com/pulse/how-copypaste-power-automate-desktop-flows-another-computer-sharif/

Credits: @eetuRobo

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No
AConnelly 30 on at

Like (1)

Report

Thank you for the reply and information.

Once I have exported the solution to the V1 environment, how do I safely update the flow to V2?

That's the real issue here. Once an environment has been converted to V2, the V1 schema flows simply are not accessible. Will I have to copy and paste the code from the V1 environment, create a new flow in the V2 environment and paste it? Will that work?

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Super User 2025 Season 2 on at

Like (2)

Report

@AConnelly

I believe it will not cause any issue. Please try and let me know in case of any issues. I will try to assist you.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

Was this reply helpful? Yes No