We are interacting with an application in IE which relies on a Silverlight add on to work. We have built the process and have spied all the elements we need however when running through the process and when clicking buttons/entering data on screen/reading info off the screen, IE crashes and freezes.
We have isolated the problem to Silverlight causing the crash.
1. Is there anything we should be doing to stop the crash? We have liaised with the app monitoring team who have said it doesn't happen for users and isolated the problem to Silverlight.
2. Is there anything we should be doing to handle the crash? At the moment we have added retries which has slowed the process down significantly but the process has been able to recover up until today, as the application recovered in the background and it was just a matter of waiting for it to do this and continuing to work on the next step in the process for that case. Today, however, the application has not been recovering from the crash and remains stuck/frozen. The process handles the exception, marks the case with the exception and moves onto the next one. This adds no value as we aren't actually getting the case worked. Any ideas on how to proceed?
3. Has anyone else come across the same issue? Is it Blue Prism's interaction with Silverlight which causes the crash - if so, why?
4. Users do not see the same volume of crashes(if any). We see the crash on every case we work.
We have isolated the problem to Silverlight causing the crash.
1. Is there anything we should be doing to stop the crash? We have liaised with the app monitoring team who have said it doesn't happen for users and isolated the problem to Silverlight.
2. Is there anything we should be doing to handle the crash? At the moment we have added retries which has slowed the process down significantly but the process has been able to recover up until today, as the application recovered in the background and it was just a matter of waiting for it to do this and continuing to work on the next step in the process for that case. Today, however, the application has not been recovering from the crash and remains stuck/frozen. The process handles the exception, marks the case with the exception and moves onto the next one. This adds no value as we aren't actually getting the case worked. Any ideas on how to proceed?
3. Has anyone else come across the same issue? Is it Blue Prism's interaction with Silverlight which causes the crash - if so, why?
4. Users do not see the same volume of crashes(if any). We see the crash on every case we work.