Answered

Power Automate desktop hosted machines stopped working "Encountered an unexpected error during Desktop flow initialization"

(0) Share

Report

Posted on by gabriel_ilx

As of about 5 days ago all my desktop flows running in Microsoft hosted machine groups have stopped working. I've already tried setting up another machine group, but to no success:

They seem to always fail before actually running any of my actions:

With the following cryptic error message:

Encountered an unexpected error during Desktop flow initialization: 'Microsoft.Flow.RPA.Desktop.Robin.Core.Packager.Exceptions.PackagerValidationException: A validation error occurred during project unbundling.
 at Microsoft.Flow.RPA.Desktop.Robin.Core.Packager.ProjectValidator.CreateAndReturnFinalValidationResult()
 at Microsoft.Flow.RPA.Desktop.Robin.Core.Packager.ProjectValidator.ValidateProject()
 at Microsoft.Flow.RPA.Desktop.Robin.Engine.Packager.PackageProvider.<>c__DisplayClass11_0.<UnbundleProjectToDirectory>b__0()
 at Microsoft.Flow.RPA.Desktop.Robin.Engine.Packager.PackageProvider.ExecuteAndLogOperation(String methodName, Action action, Func`1 func)
 at Microsoft.Flow.RPA.Desktop.Robin.Engine.Packager.PackageHelper.PackProjectToDirectory(Byte[] projectData, String directory, Guid flowId)
 at Microsoft.Flow.RPA.Agent.Server.Components.ScriptEngines.RobinEngine.DataResolvers.RootFlowDataResolverV1.GetFlowDataAndSetState(Guid scriptId, Guid runId, Dictionary`2 flowInfoCache, String directory)
 at Microsoft.Flow.RPA.Agent.Server.Components.ScriptEngines.RobinEngine.RobinScriptProvider.ResolvePackagePath(Guid flowId)
--- End of stack trace from previous location where exception was thrown ---
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 at Microsoft.Flow.RPA.Agent.Server.Components.ScriptEngines.RobinEngine.RobinEngine.<Execute>d__21.MoveNext()'.

Categories:

Power Automate Desktop

All responses (6)

Answers (1)

Sort by

kenseongtan Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

@gabriel_ilx , I'm checking this with the team and will get back to you with updates.
Verified answer

KD_IA_Forvis 9 on at

Like
a
(1)

Report
Copy link

Link copied!

@gabriel_ilx and @kenseongtan

Our team encountered the same issue for a client after we performed the Power Automate Desktop updates to version 2.29.127.23042 where we have a number of actions that pull files down from SharePoint Online and use the "Convert Binary to File" action that are no longer working.

At this time, the issue appears to be the SharePoint actions are outputting as "Connector Object" and not binary.

Our current work around for this issue is using a "Set Variable" action and updating its name to the same as the output variable name for the get content actions.

#FORVIS #Insights&Automation
Mikumasa 8 on at

Like
a
(0)

Report
Copy link

Link copied!

Just leaving my mark to get the notice. Facing same problem.
rkauzlick_IA 2 on at

Like
a
(0)

Report
Copy link

Link copied!

@Mikumasa have you looked at the solution provided by @KD_IA_Forvis? This approach solved the issue we were having.
kenseongtan Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Everyone,

Just to provide an update, indeed the failures are related to the Sharepoint (Preview) actions, with the the use of "Convert Binary to File". This is a known issue in 2.29 version of PAD and the options to workaround are:
Option 1: Using a "Set Variable" action
Option 2: Roll back to 2.28 version of PAD

As the hosted machine group will always provision the machines with the latest version of PAD, so the only available workaround for now is Option 1, until the known issue is resolved in a newer version of PAD.

Thank you.
gabriel_ilx 30 on at

Like
a
(1)

Report
Copy link

Link copied!

The workaround described by @KD_IA_Forvis and confirmed by @kenseongtan did indeed work for me, thanks!