No available Automation device Using xxxx: No such cluster: Non Production1

When configuring Robotic Process Automation (RPA) in the integrations tab of KTA (Kofax TotalAgility), there are two options: .NET and REST. In this case, they initially configured it to use .NET.

However, it's important to note that .NET relies on the RoboServer Settings configuration, while REST utilizes the settings defined in the Management console.

In the specific scenario mentioned, the Roboserver.setting file of the organization had the cluster name set as "Non Production1." Since they were trying to use .NET, it was searching for the "Non Production" cluster defined within the Management console but couldn't find it. To resolve this issue, they had to update the roboserver.setting file with the correct cluster name.

The problem was discovered when they attempted to run and call the robot using REST instead of .NET, which worked successfully.