Unanswered

The run has exceeded the queue waiting time limit. Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.

(0) Share

Report

Posted on by jsteele64289

Hi all!

This error was showing this morning across a client's environment. All scheduled and triggered processes failed this morning, with this error message, despite there having been no queue on any process or machine involved, for at least the three previous days.

This was a catastrophic failure, as it prevented all of the client's normal automations from completing this morning. I am curious if anyone else has seen this issue, and if so, what was the root cause? Is there a known fix?

Also does anyone know why this type of error takes three hours of "sitting there" for the process to acknowledge this was the error? I realize the documentation indicates various wait times and delays for allowing the process to fail in certain situations and for certain error messages, but it seems like a "queue" being overloaded would cause an immediate failure, as it would be a "known state" and Power Automate would not need to await a response to explain why the run could not complete.

Thanks for any help you can provide!

Categories:

General topics

I have the same question (0)

All responses (6)

Answers (0)

AC_Sean 2 on at

Like (0)

Report
Copy link

Link copied!

Started having the same issue this morning, can't get any cloud flows running, they all just sit in the Run Queue underneath this one that the parent cloud flow failed, but the associated running desktop flow still shows as the current queued flow. Were you able to get this resolved?

Was this reply helpful? Yes No
Tomeo 2 on at

Like (0)

Report
Copy link

Link copied!

Any fixes found for this issue? We have a number of desktop flows which are triggered by the cloud, but in recent weeks we have started to notice the odd desktop flow failing to trigger, which in turn makes everything else sit in a queue. The error claims that the endpoint was not found, unfortunately it spent 3 hours in a queue waiting before coming to this conclusion. In the meantime, it collected up 20+ desktop flows which also sat queued and remained so after the initial flow failure.

Was this reply helpful? Yes No
MB-29080635-0 18 on at

Like (0)

Report
Copy link

Link copied!

We have the same problem, is there already any solution for this?

Was this reply helpful? Yes No
RichPapp 2 on at

Like (0)

Report
Copy link

Link copied!

Sadly this is now occurring with us also. Why is MS not more proactive to explain how to clear the queue, prevent it in the future, etc.
Did you ever get a response?

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

Like (0)

Report
Copy link

Link copied!

Power Automate has a time limit for its flow in the queue. A flow can stay in the queue for 3 hours and then the flow fails.

The error occurred because may be one of your flow is running for more than 3 hours and the other flows in the queue failed because it was in the queue kept waiting for more than 3 hours.

If you think I have answered your question please mark this.

Was this reply helpful? Yes No
dsjijo 2 on at

Like (0)

Report
Copy link

Link copied!

I had similar issue, (The run has exceeded the queue waiting time limit. Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue. )

I am not sure of what caused the issue at my side but was able to rectify using the below steps.
1. Ensure no other user is using (running Power automate) the VM at the same time with your VM where PAD is running.
2. Remove the machine runtime from the cloud(connection) and recreate . I also went to the VM and opened the Power automate runtime and renamed the machine name and saved and re created the connection at the cloud.

Was this reply helpful? Yes No