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)
For me the default environment shows up in the Admin Center. I would suggest you get in touch with your admin for the access
But what if your flows are in the default environment? Can't find the default environment in the Admin Center (at least in my case).
Thank you so much for finding this solution!! I've had an issue on the rare occasion where a PAD flow gets "stuck" in the queue (canceling does nothing, perpetually shows "Status: Next Run", etc...) and holds up everything else for HOURS until it eventually resolves itself.
Your solution allows me to clear the clog immediately. This is immensely helpful! Thankyou!
Hi,
I did it yesterday and here is how you need to solve it.
Got to https://admin.powerplatform.microsoft.com/
Select Environments on the left of your screen and you should see a list of environments you have access to
Click on the environment, you are facing this problem
Click on settings, it should be at the top of the screen
Expand Data Management Tab
Click on Bulk Deletion
Click on New to create a new bulk deletion job
Click Next on the wizard menu and then set the following conditions.
You can modify the dates as you like, but i kept it like older than 2 days.
Finish through the wizard and schedule the job to run as scheduled.
This should remove all the queued items stuck forever in the monitor Desktop flow run window
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
DId you get any update from Microsoft? I am also facing the same issue
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.
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.
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...
Hello There,
In case to resolve this problem you have two options on the table
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.
WarrenBelz
146,743
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,079
Most Valuable Professional