The machine is no longer usable. Add a new machine, then update the desktop flow connections in your cloud flows to use the new machine. Adding more machines would help distribute the workload. The machine is busy. If your desktop flow times out after the three hour time period, it is likely that the allocated machine resources are not sufficiently scaling to meet the workflow demand. The machine is offline. Start up your machine, then make sure that Power Automate Desktop is properly installed and the on-premise gateway is active. There can be several reasons why your desktop flow times out with a NoCandidateMachine error: If no machine is available after three hours since the time it was requested, the desktop flow will time out and fail with a NoCandidateMachine error. Once a machine is available, the next desktop flow run will be selected based on priority and time of request. When there are no available machines, Power Automate will create a queue that holds the desktop flows waiting to be run. Your desktop flow failed to run with the error code NoCandidateMachine or the error details "No machine able to run the desktop flow has been found". No machine able to run the desktop flow has been found
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |