Answered

Desktop flow error code "ExecutionStatusNotTerminal"

(1) 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 (15)

Answers (1)

Sort by

Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(1)

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 15 on at

Like
a
(3)

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
SE-20041415-0 30 on at

Like
a
(1)

Report
Copy link

Link copied!

@michaelastrauss these errors are indeed new to us just after updating the power automate desktop version on that server. We have updated the version on another server and are now experiencing the same error code there. Similar to you with around 5 or more times per day runs failing on this error code.

I have looked at the suggestions made by @Sunil Kumar Pashikanti (for which thanks!). However, we did not find any events or installation errors. Also using the various troubleshooter reports from the runtime app we were not able to find any causes.

On another note, the server where we first experienced the issues has been replaced to another server to check if that solves the problem. However, it did not and the error codes keep appearing multiple times per day.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

@SE-20041415-0,

Thanks for confirming, the timing around the recent PAD upgrade is really helpful context.

To help narrow this down a bit further:

Have you already raised a Microsoft support ticket for this issue? If so, do you have a case number and any correlation IDs from failed runs?
The reason I’m asking is to understand whether this is already in Microsoft’s escalation pipeline, if this is a PAD regression, community troubleshooting alone won’t resolve it.

Have you tried rolling Power Automate Desktop back to a previously stable version on at least one machine (with auto‑updates disabled) to see if the issue persists?

Since the problem started immediately after the upgrade and is now occurring across multiple machines, this does point more toward a PAD runtime regression rather than a machine‑specific configuration issue. Being able to confirm this via rollback would be very useful for escalation.

Was this reply helpful? Yes No
SE-20041415-0 30 on at

Like
a
(1)

Report
Copy link

Link copied!

@Sunil Kumar Pashikanti I already checked but saw on this link that rollback is not possible? https://learn.microsoft.com/en-us/power-automate/desktop-flows/how-to/update_power_automate

If it is possible, how could we test/try that?

On your remark of Microsoft support ticket, no we have not raised a support ticket issue. Where could we do this?

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @SE-20041415-0,

You’re right that Power Automate Desktop does not support an in‑place rollback once updated. When rollback is mentioned in this context, it’s meant purely as a validation step, not a supported production action. For example, confirming behavior on a separate test VM or machine that hasn’t yet been updated. The goal is only to confirm whether this is a runtime regression in the latest PAD version, which helps Microsoft engineering investigate.

Since this issue started immediately after the upgrade and now reproduces across multiple machines, the next recommended step is to open a Microsoft support ticket.

You can do this from the Power Platform Admin Center:

URL: admin.powerplatform.microsoft.com/support/requests
Left navigation shows Support → Support requests
You see a “Get support” button
On the right, there’s a Support agent (Preview) panel with steps: Issue → Interview → Solutions → Support

This is the correct Power Platform Admin Center support experience for raising a Power Automate / PAD support ticket.

This allows Microsoft to review backend telemetry and agent diagnostics that aren’t visible from the community side.
At this point, investigation on the Microsoft side is required.

Exact steps to create a Microsoft support ticket (based on the screenshot attached)
Follow these steps exactly from where you are now:
Step 1: Start the request

Click the Get support button (left side, green button)

This opens the Support agent (Preview) flow you already see on the right.

Step 2: Describe the issue (IMPORTANT)
In the text box that says “Describe the issue that you need help with”, paste a clear summary, for example:

Power Automate Desktop unattended flows are intermittently failing with error code ExecutionStatusNotTerminal.
The issue started immediately after upgrading PAD to version 2.67.143.26090 and reproduces across multiple machines and machine groups.
Flows run for several minutes but return no action logs. Machine replacement did not resolve the issue.

Then click the Send / arrow button.

Step 3: Interview phase
The Support agent will:

Ask clarifying questions (product, scope, impact)
Propose self‑help or known issues

If a suggested solution does not apply, explicitly choose “This did not solve my issue”.
This is important, it unlocks escalation.

Step 4: Move to “Support” (human escalation)
Once self‑help is exhausted, the flow will present an option similar to:

Contact Microsoft Support
Create a support request

Select that option.
You’ll then be asked to:

Choose Product: Power Automate / Power Automate Desktop
Choose the Environment
Set Severity
Provide contact details

Step 5: Submit
After submission:

A support request / case number is generated
The ticket appears in the Support requests list (left panel)
Microsoft support may follow up asking for:

Correlation IDs
Machine runtime logs
Confirmation of version and timeline

Was this reply helpful? Yes No
SE-20041415-0 30 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Sunil Kumar Pashikanti,

Thanks for your help. I have made a support request this morning. For further context, yesterday we had to update Power Automate Desktop on another server due to a flow being updated on a newer version than the version on the server. Now the error code has appeared on that server as well for the first time. So more and more clues are pointing towards the PAD Update version. Will keep you all posted.

Was this reply helpful? Yes No
SE-20041415-0 30 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Sunil Kumar Pashikanti @michaelastrauss,

Update from my side now I have been in contact with Microsoft. It is now a known issue with the workaround to uninstall the current PAD version and install the latest version of 2.65. In 2 weeks 2.68 should be released which should fix the issues.

I managed to find the installer file for 2.65 on this github link as I was not able to find an official Microsoft page showing installer files from older versions: https://github.com/jfevia/Power-Automate-Desktop/releases.
* Microsoft just sent me an official link: https://download.microsoft.com/download/981e5163-4a96-43e2-b650-c90324122bd4/Setup.Microsoft.PowerAutomate.exe

I am now keeping an eye on one of our machines that now has 2.65 installed to see if that solves the problem.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @SE-20041415-0,

Thanks a lot for taking the initiative to reach out to Microsoft and sharing this update, really appreciate the effort here 👍 This is very helpful information for others in the community who might be facing the same issue.

This lines up with what we’ve been seeing on our side. We were encountering intermittent desktop flow failures with the ExecutionStatusNotTerminal error, so this could explain the root cause if the installation ended up in a partial or inconsistent state due to the security policy.

Rolling back to 2.65 sounds like a solid workaround for now. Good call on monitoring the machine with 2.65, that should give a clear indication if things stabilize. Let’s also keep an eye out for 2.68 as the permanent fix.

✅ 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
SE-20041415-0 30 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Sunil Kumar Pashikanti

Rolling back to 2.65 would work if you have flows running that are created/last edited on that version or older. Unfortunately this is not the case for us so we had to reinstall the latest versions to allow the machines to run the flow. I have contacted Microsoft about this and they will get back to me.

Was this reply helpful? Yes No