Unanswered

Desktop flow fails with ExecutionStatusNotTerminal

(0) Share

Report

Posted on by MichaelSchweer1

Hi,

Lately I've had a few desktop flows fail with ExecutionStatusNotTerminal as error and "Encountered internal server error." in details. The same flows then run fine for a while before suddenly failing the same way again. They are all triggered in cloud flows.

Have anybody seen something similar?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Riyaz_riz11 4,120 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @MichaelSchweer1 ,

Did you get a chance to check what error you got, connection error or flow error, or PAD action error, you can check from cloud using desktop flow activity.

If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

Regards,
Riyaz

Was this reply helpful? Yes No
MichaelSchweer1 9 on at

Like (1)

Report
Copy link

Link copied!

Hi @Ahammad_Riyaz

In the flow run details it says that it ran for 43 minutes before failing. But where the actions are supposed to be it says "Unable to display actions" and "The desktop flow has failed before starting the execution on the machine."

But it did run for about 43 minutes. I log to an SQL database from the desktop flow, so that part I am sure of.

Was this reply helpful? Yes No
AK88 453 on at

Like (1)

Report
Copy link

Link copied!

Hi @MichaelSchweer1 ,

Kindly check the particular desktop flow actions status from the tab 'Desktop Flow Activity'. check the last runs and if you open you can see the flow execution details. Kindly check and paste here what is the exact error you're getting.

Thanks,
if my response gives hint for your query kindly provide Thumps UP

Was this reply helpful? Yes No
MichaelSchweer1 9 on at

Like (0)

Report
Copy link

Link copied!

I can't see any actions and I think it is because it is the PAD client itself that crashes.

In event viewer I get a .NET Runtime error:
Application: Microsoft.Flow.RPA.Agent.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.Flow.RPA.Agent.Server.Components.ScriptEngines.RobinEngine.RobinEngine+<Agent_RunCompletedAsync>d__35.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

and an Application error:
Faulting application name: Microsoft.Flow.RPA.Agent.exe, version: 2.42.317.24061, time stamp: 0xceafd3ff
Faulting module name: KERNELBASE.dll, version: 10.0.20348.2461, time stamp: 0x6008e061
Exception code: 0xe0434352
Fault offset: 0x000000000003f19c
Faulting process id: 0x2490
Faulting application start time: 0x01dab1076332020e
Faulting application path: C:\Program Files (x86)\Power Automate Desktop\Microsoft.Flow.RPA.Agent.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: e4de1d7a-5892-4623-a729-ea98bda68c97
Faulting package full name:
Faulting package-relative application ID:

It only started happening about a month ago. The same flows had been running fine before without encountering the ExecutionStatusNotTerminal error.

Was this reply helpful? Yes No
KC Maringanti 24 on at

Like (0)

Report
Copy link

Link copied!

Hello Everyone,

We started seeing the same issue from a week or so.

Up on research, we found that this is happening when multiple cloud flows are triggered at the same time trying to launch desktop flow on the same machine.

Whenever this issue occurs, the desktop flow does not complete, and the logs are not uploaded to Power Platform. However, the next run in the queue continues smoothly.

There are 2 challenges with this:

1. We do not what happened in the process for the given run

2. if any transaction is interrupted between, then there is a risk of incorrect processing which may impact our business

I hope Microsoft fixes this ASAP.

Was this reply helpful? Yes No