Can't run flow - Requested agent is not reachable

[Anonymous]

Hello!

I have a flow created in Power Automate Desktop. It is for web automation and runs on a webpage. The flow works fine in attended mode (triggered by a button in the app), however, when I try to run unattended it only works about 1/4 times. When it doesn't run I get the following error: ''There's an issue starting your desktop flow. Requested agent is not reachable. Check for errors and try running it again.'' I don't think there are any errors in the flow as it works in attended mode. 

This is shown in output-body: 

{

  "error": {

    "code": "InternalServerError",

    "message": "Requested agent is not reachable."

  }

}

I am connected directly to a machine (user is signed out) and I have tried using a gateway but the issue remains. Do you have any suggestions on how this can be solved?

Thank you! 

[RPAdeveloper]

Hello, I get the same error.

Are there any suggestions for the matter?

Thanks in advance.

[Anonymous]

Hello.

I created a new VM that was much faster in general and on start-up and it solved the problem, everything works fine now. I think it might have been caused by the fact that the first VM I used was not powerful/fast enough.

Hope it helps, good luck! 

[Kanika_arora]

Hi,

I already have very good configuration in the VM & still this type of errors comes up frequently- rpa agent is not responsive, requested agent is not reachable, encountered internal server error, etc.

Are there any other suggestions to fix this?

Thanks in Advance.

[Krishna30]

Hi,

I'm also getting the same error while triggering the desktop flow from the cloud flow by using the unattended mode. The RDP Machine is faster enough to run the flow. Also it's working fine before. I'm not sure what's causing this issue. It's working fine on 1/5 attempts. Is any one able to figure out the solution?

[elaaboum]

Could you upgrade to the latest version of Power Automate Desktop and see if you still get this error ?

[Robottimies]

I encountered the same problem more often while running: AgentNotReachable. I restarted the machine and the first run now went through. The problem of mystery 😀

[sdeymonnaz]

Hi, I am getting this error messages as well as "rpa agent is not responsive" a lot running Power Automate Desktop flows in unattended mode in a VM using machine direct. Is there a solution for this?

[Robottimies]

The same problem persists. Today, several runs crashed into this. Restarting helped. I hope there is a solution to this 🤔

[HrishiD]

I am getting same error Requested agent is not reachable as well as the rpa agent is not responsive.

Anyone found cause or fix of it?

[earljanff]

Hello, I am still receiving this error.

Is there a known solution for this or is restarting the virtual machine is still what solves this?

Thank you.

[Robottimies]

I haven't received a response to this myself, although I did make an organization-specific support ticket to Microsoft on the subject. Now, there have been no errors for several weeks/months. What was suspected when the topic was discussed, that the fault would be on the computer that runs the desktop flow. I will continue to investigate further if this problem is activated by us again.

[Robottimies]

By bad.. That I went to say that there were no problems for the moment 😅. Now they started again, as a error message: The customer service is not reachable.

The problem usually occurs in the morning around 03-06:00. I suspect that there is something in the computer itself that runs the desktop workflow that breaks the connection to the machine. However, even our IT expert could not find the reason.

I need to send a support ticket to Microsoft again, if they know what it's the reason.

[Yogeshgade]

Hello Guys,

Same problem occured with me,but We were found issue in machine hanging that's why unable to respond desktop agent,

I think everyone use this solution if you have same issue , just try to analyse there is any bot stuck in unattended mode and please ensure that you were handle exceptions for all conditional failures,

Suppose unattended bot stuck and its wait for window(another any type of action cause process thow exception) then it's not able to end the session it's trying to search that window then machine not able to respond properly.

You need to analyse proper exception handling for all unattened bots as well as check minimum required machine configuration.

If you have resolved your problem by using this solution please mark as a solution.

[Yogeshgade]

Hello Guys,

Same problem occured with me,but We were found issue in machine hanging that's why unable to respond desktop agent,

I think everyone use this solution if you have same issue , just try to analyse there is any bot stuck in unattended mode and please ensure that you were handle exceptions for all conditional failures,

Suppose unattended bot stuck and its wait for window(another any type of action cause process thow exception) then it's not able to end the session it's trying to search that window then machine not able to respond properly.

You need to analyse proper exception handling for all unattened bots as well as check minimum required machine configuration.

If you have resolved your problem by using this solution please mark as a solution.