Unanswered

Desktop flow error code "ExecutionStatusNotTerminal"

(0) Share

Report

Posted on by SE-20041415-0

While running a desktop flow on an unattended server I am getting the error code "ExecutionStatusNotTerminal" with the error message "Encountered internal server error.". I have multiple servers where I run unattended flows and this specific server is the only one that has given me this error code.

It happens while running different desktop flows. Which most of the time run succesfully but every now and then they fail with this error. I am not able to view the desktop flow action details as it shows:

Unable to display actions

The desktop flow has failed before starting the execution on the machine.

At the same time I can see that it actually executed for multiple minutes in the server so there should be actions in the details log. I also tried to find out if it fails at the same length of running, but that varies as well with run times ranging from 3 minutes to 14 minutes.

In order to fix this issue I have:

Updated Power Automate Desktop to the newest version
After that did not work, removed and reinstalled Power Automate Desktop
Increased the agent ping timeout in the registry editor
Looked at the Event viewer at the times that the flows failed but saw no clear warning or error events

Does anyone have an idea on how to fix this?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Sunil Kumar Pashikanti 1,872 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi @SE-20041415-0,

Do Event Viewer logs show Microsoft.Flow.RPA.Agent.exe crashes?

Is the server using MSI or Microsoft Store PAD version only?

Are antivirus or EDR tools installed on this server?

Does restarting the Power Automate service temporarily fix the issue?

This is a known PAD unattended runtime issue. ExecutionStatusNotTerminal usually means the PAD agent crashed or lost connectivity mid-run, not that the flow logic failed. The run actually starts, but the agent never returns a terminal status, so actions cannot be displayed.

Focus on the machine, not the flow. Check Event Viewer for Microsoft.Flow.RPA.Agent.exe .NET crashes, validate network access to Power Platform endpoints, ensure only one PAD install type is present, and run the Machine Runtime troubleshooter. Similar cases are already reported in the Power Platform Community, so this appears to be a duplicate.

https://community.powerplatform.com/forums/thread/details/?threadid=df066f91-0969-490c-b5c1-2c0fc047caf9

Recommended Actions (Actionable)
1. Confirm agent crash

Check Event Viewer > Application
Look specifically for.NET Runtime errors for Microsoft.Flow.RPA.Agent.exe
This exact failure pattern has been reported by others.

2. Run PAD Troubleshooter

Open Power Automate Machine Runtime
Go to Troubleshoot > Diagnose connectivity
Ensure access to required endpoints
This is Microsoft’s primary diagnostic path.

Troubleshoot desktop flows runtime - Power Automate | Microsoft Learn

3. Validate machine networking and stability

Check firewalls, proxies, AV, and endpoint protection
Ensure no intermittent drops to:

*.servicebus.windows.net
*.api.powerplatform.com
*.dynamics.com
Connectivity instability commonly causes non-terminal failures.

Troubleshoot unattended desktop flow execution failures - Power Automate | Microsoft Learn

4. Verify clean PAD installation

Ensure only one PAD installation type (MSI or Store, not both)
Remove orphaned services after uninstall
Mixed installs are unsupported and cause runtime crashes.

5. Enable defensive flow diagnostics

Add On block error at top level
Log heartbeat entries to file or DB
Capture screenshots on error
Helps confirm exactly where the agent stops responding.

Alternate suggestions

Temporarily move flows to a different machine group to confirm machine-specific root cause
Reduce long-running unattended sequences by splitting flows
Wrap the PAD call in a cloud flow retry policy
If reproducible, open a Microsoft support ticket with correlation IDs

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/

Was this reply helpful? Yes No
michaelastrauss 4 on at

Like (1)

Report
Copy link

Link copied!

As one bit of further information - We just began receiving these same errors after we updated to the latest version of PAD on our servers.
We updated on the 19th. There were no references to this error at all as far back as December of 2025. The upgrade was applied on Sunday the 19th and Monday at 6am, we had our first 'ExecutionStatusNotTerminal' message. We updated to Version: 2.67.143.26090.
We are now getting two (2) to five (5) of these per day on an assortment of PADs and on both servers (we have two servers grouped together).

This could be coincidental but it does seem suspect. We will continue investigating per the recommendations given.

Was this reply helpful? Yes No