Unhandled error when opening my flow on coworkers PC.

[LogicSmith]

We have encountered an Unhandled Error when attempting to edit a flow on a coworker's PC. Backstory is...

Coworker and I installed Power Automate Desktop. I created some desktop flows. Version on both is 2.20.00147.22150.

We both then got Premium. I shared my flows with coworker as co-owner.

Coworker can see my flows as shared in web app. Attempting to open for edit gives bizarre error.

This happens on any of my flows that coworker opens for edit. We're trying in reverse (me editing his flow) but still have to finish that testing.

Now comes the fun part - I have a screenshot, and I have text of the error. Let's see if I can attach or insert them...

And here's the error text...

Message = Width and Height must be non-negative.
Error = System.ArgumentException
Full text = System.ArgumentException: Width and Height must be non-negative.
at System.Windows.Size..ctor(Double width, Double height)
at System.Windows.Controls.Grid.MeasureCell(Int32 cell, Boolean forceInfinityV)
at System.Windows.Controls.Grid.MeasureCellsGroup(Int32 cellsHead, Size referenceSize, Boolean ignoreDesiredSizeU, Boolean forceInfinityV, Boolean& hasDesiredSizeUChanged)
at System.Windows.Controls.Grid.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Controls.Border.MeasureOverride(Size constraint)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Window.MeasureOverrideHelper(Size constraint)
at System.Windows.Window.MeasureOverride(Size availableSize)
at System.Windows.FrameworkElement.MeasureCore(Size availableSize)
at System.Windows.UIElement.Measure(Size availableSize)
at System.Windows.Interop.HwndSource.SetLayoutSize()
at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value)
at System.Windows.Window.SetRootVisual()
at System.Windows.Window.SetRootVisualAndUpdateSTC()
at System.Windows.Window.SetupInitialState(Double requestedTop, Double requestedLeft, Double requestedWidth, Double requestedHeight)
at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.ShowDialog()
at Microsoft.Flow.RPA.Desktop.Shared.UI.Dialogs.DialogWindow.ShowDialog()
at Microsoft.Flow.RPA.Desktop.Shared.UI.Dialogs.DialogService.ShowArbitraryContent(Window owner, Object content, String caption, Object titleTemplateKey, Object contentTemplateKey, DialogOptions options, Func`3 closingCallback)
at Microsoft.Flow.RPA.Desktop.Common.UI.TeachingGuideService.TeachingGuideStepsConfiguration.ShowDialog(Object content, String caption)
at Microsoft.Flow.RPA.Desktop.Common.UI.TeachingGuideService.TeachingGuideService.ExecuteStep(GuideStep step)
at Microsoft.Flow.RPA.Desktop.Common.UI.TeachingGuideService.TeachingGuideService.Start(String groupName)
at Microsoft.Flow.RPA.Desktop.Designer.Host.MainViewModel.<InitializeAsync>d__180.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Flow.RPA.Desktop.Shared.Common.Extensions.TaskExtensions.<FireAndForget>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

[LogicSmith]

The reverse test shows no error. My coworker created a desktop flow, saved, ran, shared (from flow.microsoft.com), and I was able to edit it and run it with no issues. Although, the modification I made (message box text) and saved did NOT show up on his PC - that still shows his original message.

So I'm wondering if something is odd on his machine that is not on mine. I do run PAD as administrator, not sure if he did or not.

[LogicSmith]

More background on this one. On my laptop, apparently it is setup as a device with a local (admin) account and is not joined to Azure Active Directory. My coworker's laptop is joined to Azure AD, and he signs in with an Azure AD account. He has a separate account/password to allow local admin access. So when I run PAD as administrator, it only verifies that's what I want. When he runs PAD as administrator, he has to provide the account/password to allow that. We don't know which method is better or "most correct".

Experimentation will continue until we have this solved one way or another.

[LogicSmith]

Further information - my coworker was able to create a flow on his desktop, shared it with me, I was able to open and run it. However, when I modified it and shared it back to him, he now gets the above error on attempting to open the flow. He has also been able to create and save a new flow, and gets that error when trying to edit it. We still need to have IT fix his login issue, hopefully that will fix it, but other than uninstalling and reinstalling it, what else can we do? Since it is an actual Unhandled Error, I would hope the dev team would take an interest. Is there an official place to report obvious bugs?

[Ankesh_49]

@LogicSmith Could you please refer this video: https://youtu.be/a-iVSsg8EN8 and see if it solves your issue.
Also, this may be a problem with a changed monitor/display resolution. Would you mind checking it as well, as I am guessing it seeing the error message:

Hope it helps!! Keen to know the outcome.

[LogicSmith]

Thanks for the tip. We'll give this a try as soon as coworker comes in. As for the display resolution, it's a bit complicated. We both have identical laptops, plus three HD monitors. So, basically 4 screens, all 1920x1080.  Our systems are about as identical as possible in terms of hardware. Hopefully today we can get the login/local admin issue resolved too. But, if not, at least it's Friday, right?

[LogicSmith · Accepted solution]

Saw this post about a different Unhandled Error. Suggestion was to go to user/myname/appdata/local/microsoft and delete the folder Power Automate Desktop. He was then able to restart Power Automate and open flows without getting the Unhandled Error. So hopefully that took care of it...

[AQP_001_ROBO]

I am also facing the same issue and I have tried the and deleted the file and signed in again then also it is showing the problem with the pop up whenever I am trying to edit the flow