Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

Unable to connect to unattended robot Error 'Unable to open a connection to ServiceNow Instance

Yekbote
Tera Contributor

2 hours ago

Hello, 

 

I'm unable to connect the unattended robot to the instance even though it has necessary roles and access. It is giving the error 'Unable to open a connection to ServiceNow instance'. 

 

I've verified below things: 

1. Verified the user has 'sn_rpa_fdn.rpa_robot' role. 

2. The installed version has the latest one. 

3. The robot credential record has the username in correct format [domain\username]

 

Note: Initially I was able to connect the robot to the instance. I'm unable to re-connect it after disconnecting. 

 

Can someone help me to fix the issue. 

Regards,
Bhavani.

0 Helpfuls
  • 91 Views
2 REPLIES 2

sachinvic
Kilo Guru

an hour ago

@Yekbote 

Hi Yekbote,

Since the robot was connecting fine initially and the issue only started after disconnecting, you're likely dealing with an authentication handshake failure, or a network session drop rather than a broken role configuration. You shouldn't re-configure the whole setup just yet since you've already confirmed the role and credentials format.

 

First, double-check the RPA Hub authentication settings in your instance and make sure they completely align with whatever method you configured on the robot client side. To rule out any weird user profile or permission conflicts, it's usually best to test the connection using a dedicated, local functional ServiceNow user that has the sn_rpa_fdn.rpa_robot role explicitly assigned, rather than using your day-to-day account.

 

If the credentials are checked out, take a close look at the local environment. If that machine sits behind an enterprise proxy, verify the proxy configuration rules to confirm the robot can reach out to the instance. While you're in there, double-check that the configured Instance URL hasn't been changed or typoed. Even though you mentioned the latest MSI is installed, it is still worth verifying the version compatibility matrix between that specific Unattended Robot build and your current RPA Hub plugin version, just in case an instance update threw them out of sync.

 

You should check the auth settings and the dedicated robot user first and then move down to the network and proxy troubleshooting if it still won't connect.

 

If you want to review the baseline environment and port requirements, the official setup steps kindly go through the this link : https://www.servicenow.com/docs/r/integrate-applications/set-up-rpa-runtime.html

0 Helpfuls