Answered

The flow was not able to start running. The flow and its dependencies were not retrieved properly.

(1) Share

Report

Posted on by Calebm

Hello,

I created a desktop flow that works perfectly fine when opened and run in the editor, but when I try to run it using the Play button, I get the following error message:

The flow was not able to start running. The flow and its dependencies were not retrieved properly.

Correlation Id: 6182d08c-588a-4311-aa0d-aba3529623be
Sequence contains more than one matching element

Has anyone else experienced this or know what could possibly cause it?

Categories:

Power Automate Desktop

2025-03-28-PadCon...

I have the same question (0)

All responses (9)

Answers (2)

ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (0)

Report

What is the flow actually doing?

Was this reply helpful? Yes No
Michael E. Gernaey 53,360 Super User 2025 Season 2 on at

Like (0)

Report

H i@Calebm

Who is the flow running as (in the editor it is you and is an admin). If for any reason it doesnt have access to those things, when you are running in play mode you would see this.

Was this reply helpful? Yes No
Verified answer

KYSCARTI 36 on at

Like (2)

Report

I have the same issue, I have manually downgraded to version 2.53.186.25057 https://github.com/jfevia/Power-Automate-Desktop/releases. My problem now is sometimes even though I downgraded it keeps Auto Updating it again. Hopefully, they get it fixed soon.

Was this reply helpful? Yes No
Calebm 31 on at

Like (0)

Report

@Michael E. Gernaey I ran the verbose logs and it doesn't seem to be running as administrator in either case.

@ronaldwalcott the flow scrapes data from a website, opens documents from the website in the browser, prints the documents to PDF, and flags the printed documents as processed.

I ran the troubleshooter and it said I had an issue because I had two versions of Power Automate installed (even though one of them is just the machine runtime app), I tried uninstalling that and then running the flow and that did not work. The troubleshooter also threw this error for Web Automation:

It is worth noting that the flow I'm having issues with is a save-as from another flow with a bit less functionality, and the original simpler flow worked fine. In addition, I have shared this flow with a coworker (both under trial Premium licenses) and both of us are experiencing the issue.

Was this reply helpful? Yes No
Verified answer

Nycolas Oliveira 18 on at

Like (1)

Report

Hello everyone!

I was encountering exactly the same problem, but in flows that used selectors from the "Power Automate Agent for virtual desktop". All I had to do was create a blank flow and add a selector of this type and the error would appear.

But today (02 Apr 2025) I noticed a new update in the PAD client, so after completing the update to version 2.55.158.25087 the problem was solved, I no longer encounter any errors of this kind and no editing was necessary in the flows.

Was this reply helpful? Yes No
KYSCARTI 36 on at

Like (0)

Report

Nycolas Oliveira, what region are you in? I tried to update but it is still showing 2.54 as the latest version.

Was this reply helpful? Yes No
Calebm 31 on at

Like (0)

Report

@KYSCARTI Your solution worked for me, though it's not ideal as it is affecting other users downstream who I've shared the flows with as well. I would guess Nycolas is in one of the regions at the top of this page and that the page just hasnt' been updated yet. Released versions for Power Automate for desktop - Release Notes | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

Calebm 31 on at

Like (2)

Report

@Nycolas Oliveira I just realized I must have added a 'Power Automate Agent for virtual desktop' action to the flow at one point and then deleted it later. I was able to publish all my UI elements to a collection, import them into a new flow, and copy all of the subflows into the new flow, and now I no longer have the issue!

Was this reply helpful? Yes No
KYSCARTI 36 on at

Like (0)

Report

@Calebm Yeah, that's true it not ideal at all and I hate it.

The one thing I see common that we are all using Virtual Desktop or Virtual UI Elements.

Was this reply helpful? Yes No