Blue Prism 6.6 should throw an error at the point where the Process cannot interact with the element
spied using Region mode. It instead just hangs and the session goes in to a warning state.
We could see more than RTR is running in same VM.
We did a global settings in application modeler but got the same error (Warning and No Exception).
In the above case, Blue Prism should handle this type of situation by throwing an error and terminating the Session would be more informative
and quicker at alerting the problem than not notifying at all and losing valuable running time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.