- Getting started
- Host administration
- Organizations
- Tenants and services
- Authentication and security
- Licensing
- Accounts and roles
- External applications
- Testing in your organization
- AI Trust Layer
- Notifications
- Logging
- Troubleshooting
- About troubleshooting
- Alerts troubleshooting
- General troubleshooting
Automation Suite admin guide
System emails are not sent - SslHandshakeException
For offline installations, if system emails are not sent and you encounter the error SslHandshakeException, make sure that both port 80 and port 587 are opened for the machine (single node | multi-node).
Not receiving alerts for groups with SAML provisioning rule
Problem: Users do not receive configured alerts either in the user interface or via email when those alerts are configured for user groups with a SAML provisioning rule.
Solution: To resolve this issue, you can add affected users to the Administrators local group which allows them to receive alerts.
Adding users to the Administrators group grants them with elevated privileges. Endeavor to understand the implications of these privileges. Ensure users are conferred administrator rights responsibly, maintaining a balance between the need for alerts access and preserving system security.
Start jobs errors: Cannot find a personal robot configured
Description: Starting a job from My Workspace or using Run as Myself fails with error 409 UserDoesNotHaveRobot: Cannot find a personal robot configured. This occurs when no personal robot has been provisioned for the current user.
Solution: Use one of the following options to provision the required robot identity:
- On EKS/AKS and OpenShift deployments, open Studio Web once by navigating to your tenant URL — this triggers automatic provisioning.
- Connect UiPath Assistant to Orchestrator and ensure a named user license is available.
- Enable unattended automation for the user via Tenant > Manage Access > Edit User > Enterprise Setup.
After provisioning, retry the job.