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