Daily restart of digital workers - some of the digital workers unable to establish connection to app server.

[UdayB]

We have a DR ecosystem with close to 350 digital workers , 5 app servers and 5 controllers with approxiamte equal distribution of DWs across the app servers. The Blueprism version is v6.7.
A daily scheduled script remotely restarts all the digital workers (in two batches of 100 and 250) between 1:00 AM - 2:30 AM

We have observed that after the digital workers are restarted, approximately 30 -35 DWs (~10%) are unable to establish connection with their respective app servers. The Automate.exe kicks up on each of these digital workers, but either the listener startup process or the connectivity establishment process seems to be failing resulting in the digital worker not showing up as online in the control room.

As a part of troubleshooting this issue, restarting the digital worker once again seems to fix the connectivity issue. 
In some cases, the connectivity is established by itself after some time. 
The windows event log show a warning for the blue prism process right after the digital worker restart, where the connection timed out.


The concern with this inconsistent behavior is that the digital workers that have issues with connectivity may have scheduled processes, that fail to kick-in due to the digital worker having issues with connectivity to the app server.

My question is :
1. Is it recommended to restart the digital workers on a daily basis, if there are no obvious performance issues ?
2. Has anyone else observed this kind of connectivity issues in their blue prism environments ?
3. Do you have any pointers about troubleshooting the connectivity issue ?




------------------------------
Uday B
Solution Designer
------------------------------

[expertcr · Accepted solution]

Hello Uday

Well looks like your environment is very big.

Regarding your questions:
1. Yes, we recommend restarting daily the RR, is a good practice to avoid any problem with memory use that crash or freeze the applications running.
2. We see connectivity problems when they they have some problems in their network environment, we provide a PDF file with a guide to test any possible issue.
3. Al depends on each case, long network latency, DNS issues, etc.

This will be a good case to contact us over support@blueprism.com or create a ticket over the portal, you will need one of the engineers to help to locate the root cause working with your team, very possible over a Webex conference.

Have a good day.

------------------------------
Luis Lopez
Customer Support Engineer English and Spanish
Blue Prism Ltd
------------------------------