Merge pull request #9302 from MicrosoftDocs/aironefr-queue-events

AB#6596: Add links to Queue Events from pages related to NoCandidateMachine

Author: lucciz01

support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md

@@ -3,9 +3,9 @@ title: Troubleshoot desktop flow run queue-based errors
 description: Provides solutions to desktop flow queue-based error codes like NoCandidateMachine or No machine able to run the desktop flow has been found.
 author: rpapostolis # GitHub alias
 ms.author: appapaio # Microsoft alias
-ms.reviewer: befrey, lulubran, johndund, guco, fredg
+ms.reviewer: befrey, lulubran, johndund, guco, fredg, ermathon
 ms.custom: sap:Desktop flows\Power Automate for desktop errors
-ms.date: 10/08/2024
+ms.date: 07/14/2025
 ---
 # Troubleshoot desktop flow run queue errors
 
@@ -27,6 +27,10 @@ You might also receive one of these common suberror codes:
 - [AttendedUserNotLoggedIn](#attendedusernotloggedin)
 - [UIFlowAlreadyRunning](#uiflowalreadyrunning)
 
+## How to investigate
+
+You can view lifecycle events for desktop flows in the queue from the monitor run details page, specifically in the [queue events section](/power-automate/desktop-flows/monitor-run-details#view-queue-events). These events provide detailed information about each launch attempt and can help you identify the underlying root cause of queue-based errors.
+
 ## Cause
 
 When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after six hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -2,7 +2,7 @@
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
 ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon
-ms.date: 07/11/2025
+ms.date: 07/14/2025
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -50,7 +50,7 @@ _Original KB number:_   4555406
 |EndpointDoNotExist|404|Attended</br>Unattended|The endpoint wasn't found.</br>Register your machine again and schedule new runs.</br>This error typically occurs when the machine registration is deleted during the run, such as when the machine is re-registered.|
 |GroupIsEmpty|400|Attended</br>Unattended|The machine group is empty.</br> Add machines to the group, then reschedule new runs.|
 |MSEntraMachineAlwaysPromptingForPassword|400|Unattended|For more information about this error code, see [An unattended desktop flow run fails with the MSEntraMachineAlwaysPromptingForPassword error](msentramachinealwayspromptingforpassword-error.md).|
-|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.|
+|NoCandidateMachine|400|Attended</br>Unattended|The run has exceeded the queue waiting time limit.</br> Consider allocating more machines or spreading desktop flow runs to optimize wait time in the queue.</br>To solve this issue, see [Troubleshoot desktop flow run queue-based errors](troubleshoot-desktop-flow-run-queue-errors.md) and inspect the [queue events in the monitor run details page](/power-automate/desktop-flows/monitor-run-details#view-queue-events).|
 |DesktopFlowsActionThrottled|429|Attended</br>Unattended|The desktop flow action failed because of throttling. This error code appears when too many desktop flows use the same connection. Check your connection usage and assign your desktop flows to multiple connections.|
 |DesktopFlowsActionTimeout|400|Attended</br>Unattended|The execution of the desktop flow action exceeded maximum duration.</br> Increase the time-out value that's set on the action or split the desktop flow into several shorter desktop flows.|
 |OnPremiseDataGatewayNotAvailable|502|Attended</br>Unattended|This error code only occurs when using an on-premises data gateway (deprecated) to connect to the machine. Check that the targeted machine and the data gateway on that machine are up and running.|