cancel
Showing results for 
Search instead for 
Did you mean: 
Walter.Koller
Level 11
Status: Delivered

Blue Prism client/studio should be able to handle interrupted network connection.

We are working in a mobile environment moving with our laptops from meeting to meeting and to the closest working area. It happens that your laptops are changing network, going into sleep/suspend mode when closed asf.
When Blue Prism loses connection to application server, numerous .Net error messages are displayed (and lock each other so only killing the BP process helps).
Furthermore the event log of the application server is spammed with error messages, which might cause wrong alarm in monitoring tools

4 Comments
Status changed to: Needs More Info

Hello @Walter.Koller,

Thanks for taking the time to raise an idea.

A couple of versions ago, we introduced some changes to improve the resilience and recoverability of the interactive client in the event of network disruption. Can I ask what version of Blue Prism Enterprise you're currently using and whether you've seen an improvement in these issues in more recent versions?

Marking this idea as Needs More Info awaiting your reply.

Regards,

Rob

Walter.Koller
Level 11

Hello @robert.nicklin 

Thanks for the update.

We are currently using 6.9 as primary and 7.3.1 as secondary version, until the end of our upgrade transition time to 7.3.1. 

I have noticed 7.3.1 behaves much better in case of network issues. I remember a few cases when BP UI (7.3.1) stopped responding after network issue error message. 

Since this idea was created 6 years ago and improvements were made in 7.3.1, feel free to close this idea with status 'delivered'

Regards

Status changed to: Delivered

Hi @Walter.Koller,

Thank you for responding so quickly. I'm delighted to hear that you've spotted improvements in this area in BPE 7.3.1 - this was exactly what I was wanting to hear!

As a result of these updates, I'm going to mark this idea as Delivered.

Regards,

Rob

jcastellanosm
Level 4

Hi @robert.nicklin , 

Based on what we have observed in the last 3 months, all disconnects longer than 2 minutes using login via Authentication Server in 7.3.1, end with errors like 'blue prism failed to determine if user has lock' (and only killing the BP process helps).

It's especially frustrating when working over VPN connections.

Do you recommend us to use another authentication method?