The Robot status changes to unlicensed and unresponsive intermittently while being connected to a PaaS Orchestrator instance. How to resolve this?
Deployment Type:
Azure PaaS.
Issue Description:
The Robot Heartbeat signal keeps dropping between the Orchestrator and Robot machine due to which the Robot disconnects frequently.
Root Cause:
If Orchestrator and identity app services have multiple instances in the backend for the geo-replication and those instances are not synced with each other, the Orchestrator behaves abnormally.
Resolution:
Two approaches are available as listed below:
Approach #1: Reduce the Instance count to 1
Approach #2: Use the Redis (a caching mechanism) to sync the instance:
Use HAA (Cache) for the Orchestrator to sync the nodes to each other or use the Azure Redis (not tested from UiPath) then add the below keys in the App settings on the Orchestrator and Identity web app.
- AppSettings__RedisSettings__UseRedisStoreCache
- AppSettings__RedisSettings__UseRedisStoreClientCache
- AppSettings__LoadBalancerSettings__RedisConnectionString