empty URI error in get emails( V3)

(2) Share

Report

Posted on by MG-30041246-0

Hi Michael , thanks for replying. i have been stuck with this for a while. Coul you help. the flow gets error at line 8. i have left the comments from earlier steps, cant share the code for obvious reasons since it is for API access.

i have other flows with the desktop apps and all are giving the same error for get emails V3( with and without the API Code). i have attached the pic in the file.

could it be some settings in the VMS machine. please let me know.

i am still a pretty new user for desktop(3 months old)

this flow worked fine till like april 10th and then started giving the error, so I do not know what suddenly happened( nothing was changed in the flow on or before it stopped working.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Jon Unzueta 1,834 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@MG-30041246-0

it sounds like you're dealing with a persistent issue in your Power Automate Desktop flow, specifically with the "Get emails (V3)" action, and it started failing around April 10th without any changes on your end.

To help you better, I’ll need a bit more information:

Could you clarify a few things?

What is the exact error message you're seeing at line 8?

Are you using Outlook (desktop) or Outlook 365 (cloud) in the "Get emails (V3)" action?

Is your VM environment managed by your IT department (e.g., with group policies or firewall rules)?

Have you recently updated Power Automate Desktop or Outlook on the VM?

Also, if you can upload the screenshot you mentioned, I can take a closer look at the error and help pinpoint the issue.

In the meantime, here are some common causes and checks:

Authentication issues: If your flow uses a connection that expired or was revoked, it might silently fail.

Outlook profile not loaded: On VMs, sometimes Outlook isn’t fully initialized or logged in, especially if the flow runs unattended.

Recent Microsoft updates: Microsoft occasionally changes API behavior or deprecates connectors, which can break previously working flows.

Firewall or proxy changes: If your organization updated security policies, it might block certain API calls from the VM.

🏷️ Tag me if you have any further questions or if the issue persists.

✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.

❤️ Give it a Like if you found the approach useful in any way.

Was this reply helpful? Yes No
Riyaz_riz11 4,048 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

It might be due to DLP policy.

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
MG-30041246-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi all!

thank you for your responses. it was a Mcsft issue. had to raise a ticket to get it solved. all working now. thanks

Was this reply helpful? Yes No