Desktop Flow runs stuck as Queued

(1) Share

Report

Posted on by rolign

109

Hello!

Today we noticed that there is a bunch of PAD flows that are stuck as Queued in the monitoring page. They do not show up under Machine Groups, only here. Wondering whether that is something we should worry about and/or how to remove these unnecessary runs.
Machine Group queues are working fine meanwhile with new runs (apart from starting the flows with an indeterminable and random delay)

Categories:

Power Automate Desktop

I have the same question (1)

All responses (14)

Answers (1)

sruxton 2 on at

Like (0)

Report

@rolign we are having the same issue that desktop flow runs are stuck on 'queued' and won't run in unattended mode (run fine in attended) did you find a resolution?

Was this reply helpful? Yes No
rolign 109 on at

Like (0)

Report

Not really the same issue, I guess, but we did face problems with flows not starting - we did a full restart on all VMs in the particular machine group - they started to work again after.

Was this reply helpful? Yes No
thbeatty1 32 on at

Like (1)

Report

Having the same issue, did you ever find a solution? The options like 'see parent flow run' and 'cancel parent flow run' appear greyed out, so we can't remove the listings.

Was this reply helpful? Yes No
rolign 109 on at

Like (1)

Report

Nope, did not find a solution to this one - I suggest registering a support ticket via the Admin portal.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report
Hello There,

In case to resolve this problem you have two options on the table
Setup a flow as "High Priority" - perm solution
2. Go to "See desktop flow in queue" and change the priority of your flow, it will release the flow to the first availible node.

Was this reply helpful? Yes No
Sam_VionA 9 on at

Like (0)

Report

Did you even find a solution to this? I am facing the exact same problem. Runs from 3 months ago that are still in the monitoring queue...

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Stop all affected flows make sure from bots side all power automate services is running, cancel all Queued jobs and turn on the flows back again it should solve this problem.

Was this reply helpful? Yes No
thbeatty1 32 on at

Like (0)

Report

None of these solutions solve the problem for me, still receive the following error:
I have submitted a support ticket through the admin portal, will update when I receive a response.

Was this reply helpful? Yes No
rahullakshmanan 30 on at

Like (0)

Report

DId you get any update from Microsoft? I am also facing the same issue

Was this reply helpful? Yes No
thbeatty1 32 on at

Like (0)

Report

The reply I received said, among some filler language, "Our team has carefully reviewed the information you provided, and we understand that your request pertains more towards an advisory aspect." and they told me to check the forums. I replied with the research I had already completed, a link to this post, and have received no further response. Doesn't look like they will be resolving this issue any time soon

Was this reply helpful? Yes No