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

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Issue occurs after upd...
Power Automate
Unanswered

Issue occurs after updating desktop flow to v2 schema

(0) ShareShare
ReportReport
Posted on by powerbot5 4

When I edit and save the flow, it changes to v2 schema and I can't open it again and an error occurs.
This flow is referenced by many flows, so it must be able to run.
I need help.

Error Message when opening a flow:
Flow initialization failed. Please make sure there is an active internet connection and contact your administrator.

Error Message in Event Viewer:
메시지 = 'Microsoft.Flow.RPA.Desktop.Shared.Clients.DataClients.Cds.Adapters.Exceptions.DesktopFlowBinaryReferenceCollisionException' 형식의 예외가 Throw되었습니다.
오류 = Microsoft.Flow.RPA.Desktop.Shared.Clients.DataClients.Cds.Adapters.Exceptions.DesktopFlowBinaryReferenceCollisionException
전체 텍스트 = Microsoft.Flow.RPA.Desktop.Shared.Clients.DataClients.Cds.Adapters.Exceptions.DesktopFlowBinaryReferenceCollisionException: 'Microsoft.Flow.RPA.Desktop.Shared.Clients.DataClients.Cds.Adapters.Exceptions.DesktopFlowBinaryReferenceCollisionException' 형식의 예외가 Throw되었습니다.
위치: Microsoft.Flow.RPA.Desktop.Common.Services.RobinDependent.FlowPackage.FlowProjectFileProvider.GetControlRepositoriesFiles()
위치: Microsoft.Flow.RPA.Desktop.Robin.Core.Packager.ProjectProvider.GetControlRepositories()
위치: Microsoft.Flow.RPA.Desktop.Robin.Core.Packager.ProjectProvider.GetSerializedProject()
위치: Microsoft.Flow.RPA.Desktop.Common.Services.RobinDependent.RuntimePackageHelper.StoredPackageDataService.IntermediateStorePackageDataToDirectory(IPackageInfo packageInfo, Guid flowId, Guid rootFlowId, Guid runId)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.Services.Workflow.RunWorkflow.Runners.RunWorkflowBaseService.<>c__DisplayClass50_0.<PrepareWithoutErrorHandling>b__1(IPackageInfo packageInfo)
위치: Microsoft.Flow.RPA.Desktop.Shared.Utilities.LinqExtensions.ForEach[T](IEnumerable`1 source, Action`1 action)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.Services.Workflow.RunWorkflow.Runners.RunWorkflowBaseService.PrepareWithoutErrorHandling(Process workflow, Boolean isIncompatibleVersion, PackagesResultDto packagesResult, IConnectionMappingProvider customConnectionMappingProvider)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.Services.Workflow.RunWorkflow.Runners.RunWorkflowBaseService.Prepare(Process workflow, Boolean isIncompatibleVersion, PackagesResultDto packagesResult, IConnectionMappingProvider customConnectionMappingProvider)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.Services.Workflow.RunWorkflow.Runners.RunWorkflowBaseService.<DownloadAndPrepareAndRunInnerAsync>d__30.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.Services.Workflow.RunWorkflow.Runners.RunWorkflowBaseService.<DownloadAndPrepareAndRunAsync>d__29.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.ViewModel.Processes.MyProcessesTabViewModel.<StartProcessAsync>d__252.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.ViewModel.Processes.MyProcessesTabViewModel.<StartProcessInnerAsync>d__253.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.ViewModel.Processes.MyProcessesTabViewModel.<ResolveItemAndExecuteCommandAsync>d__240.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
위치: Microsoft.Flow.RPA.Desktop.Console.UI.ViewModel.Processes.MyProcessesTabViewModel.<StartProcessAsync>d__249.MoveNext()
--- 예외가 throw된 이전 위치의 스택 추적 끝 ---
위치: System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
위치: System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
위치: System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Categories:
Power Automate Desktop
I have the same question (0)
  • VishnuReddy1997 Profile Picture
    VishnuReddy1997 2,666 Super User 2026 Season 1 on at

    Hi @powerbot5 ,

     

    Please try these steps.

     

    1.Restart the Power Automate service or the computer: This is a common solution for many Power Automate Desktop issues. It’s possible that the service has failed and needs to be restarted.
    2.Check your internet connection: The error message suggests that there might be an issue with your internet connection. Please ensure that you have an active internet connection.
    3.Update Power Automate Desktop: Make sure you’re using the latest version of Power Automate Desktop. Outdated versions might have bugs or compatibility issues.
    4.Check for Proxy server related errors: If you’re using a proxy server, it might be causing some issues. Microsoft provides some steps to resolve proxy server related errors.

     

    (Note:- if you got your solution you can mark as solution and gives kudos)


    Thanks & Regards

    Vishnu Reddy

     

  • Deenuji_Loganathan_ Profile Picture
    Deenuji_Loganathan_ 6,255 Moderator on at

    @powerbot5 

     

    It's possible that this occurred due to a loss of internet connection or issues related to proxies. So, it would be advisable to focus on those areas and attempt to troubleshoot the problem.

     

    If you're unable to identify the root cause of this issue, consider reverting to schema V1 to see if it resolves the problem.

     

    If the issue resolved after reverting to schema V1, then again upgrade to schema V2 and check if it causes the same issues. If it does, attempt signing out and signing in again in PAD, or restart your system, or restart Power Automate Desktop-related services.

     


    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 🚀

  • powerbot5 Profile Picture
    powerbot5 4 on at

    Hi,

    1. The same error occurs even after restarting the computer.
    2. The internet connection is fine and only certain flows are causing this error.
    3. I'm using the latest version of Power Automate Desktop.
    4. I haven't configured any proxy server and I only get that error on certain flows.

     

    Thanks for your help, but it's not fixed yet.

  • powerbot5 Profile Picture
    powerbot5 4 on at

    Hi,

    Other flows do not throw that error when changed to schema v2...

    If I revert to schema v1 I don't get the error, but when I change back to schema v2 I get the same error.

    I tried rebooting, restarting the service, using a different account, and testing on a different PC, but it didn't work...

     

    Thanks for your help, but it doesn't work...

  • Deenuji_Loganathan_ Profile Picture
    Deenuji_Loganathan_ 6,255 Moderator on at

    @powerbot5 

     

    Please follow the below MS guide on the schema updates.

    Power Automate v2 schema - Power Automate | Microsoft Learn

     

    If nothing relevant to your issues, please raise this issue with Microsoftoft support team.

     


    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 🚀

  • AK88 Profile Picture
    AK88 453 on at

    Hi @powerbot5 ,

     

    Kindly check your environment , and enable desktop flow schema toggle. This would solve your issue.

     

     

    thanks, 

    Mark it as a solution and give Thumps Up if your problem query resolved

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

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
11manish Profile Picture

11manish 227

#2
David_MA Profile Picture

David_MA 204 Super User 2026 Season 1

#3
Valantis Profile Picture

Valantis 177

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans