Connecting a UiPath Robot to Orchestrator can be a frustrating experience, especially when encountering licensing issues or unexpected behavior. One common question that arises is what happens when a connection seemingly disappears. This article addresses the specific concern: “Dyno bot removed a link, is it gone?” We’ll explore potential causes for disconnections and guide you through troubleshooting steps to re-establish your robot connection. While we can’t definitively say what a “dyno bot” action entails without more context, we will cover common scenarios that lead to similar issues.
Understanding UiPath Robot and Orchestrator Connection
A stable connection between your UiPath Robot and Orchestrator is crucial for automation deployment and management. This connection allows you to:
- Deploy and execute automation processes.
- Manage robot licenses and allocate them efficiently.
- Monitor robot activity and performance.
- Centrally manage and control your robotic workforce.
When this connection is disrupted, your automation workflows are impacted.
Troubleshooting Disconnections
If your UiPath Robot appears disconnected from Orchestrator, several factors could be at play. Here’s a breakdown of common troubleshooting steps:
1. Verify Machine Key and Orchestrator URL
- Accuracy: Double-check that the Machine Key entered in UiPath Assistant precisely matches the one generated in Orchestrator for the corresponding machine. Even a single incorrect character can prevent connection.
- Orchestrator URL: Confirm the Orchestrator URL is correct, including the protocol (https://) and any specific subdomains. Ensure you are connecting to the correct environment (e.g., Community Cloud, Enterprise Cloud, On-Premises).
- Connectivity: Test your network connection to ensure you can reach the Orchestrator server. Firewall rules or proxy settings might be blocking communication.
2. Check License Allocation
- Sufficient Licenses: Ensure you have available and allocated unattended runtime licenses in your Orchestrator tenant. UiPath Assistant will display “Connected, Unlicensed” if a license is not available.
- License Type: Verify the license type matches the robot type (attended or unattended). An unattended robot requires an unattended runtime license.
- Allocation: Confirm the license is allocated to the correct user or machine. Navigate to the Admin section in Orchestrator and review the license allocation for your tenant.
3. Review Orchestrator Settings
- Robot Settings: In Orchestrator, navigate to the Robots section and check if the robot is registered and its status is “Available.” If the status is “Disconnected” or any other error state, investigate further.
- Machine Configuration: Ensure the machine registered in Orchestrator matches the machine where the robot is installed. This includes the hostname and user account. Any discrepancies can lead to connection issues.
- User Permissions: Confirm the user account used to connect the robot has the necessary permissions in Orchestrator to connect and execute processes.
4. Restart UiPath Services
Restarting the UiPath Robot service and the UiPath Assistant can sometimes resolve temporary connection glitches.
5. Contact UiPath Support
If you have exhausted all troubleshooting steps and the issue persists, contact UiPath support for assistance. Provide detailed information about the problem, including error messages, screenshots, and steps you’ve already taken.
Conclusion
Addressing a disconnected UiPath Robot requires a systematic approach. By verifying the Machine Key, Orchestrator URL, license allocation, Orchestrator settings, and restarting services, you can often pinpoint and resolve the issue. While the specific action of a “dyno bot” remains unclear without further context, the troubleshooting steps outlined in this article cover the most common causes of disconnection. Remember to consult the official UiPath documentation and support resources for the most up-to-date information.
