I have an adobe reader object that gets stuck in a wait stage when the application gets a Runtime Error "C++ Runtime library error R6025" (screenshot below). Although the object is set to have external timeout, it still gets stuck in a wait stage until the error dialog is manually closed. The process is shown having a Warning status in the control room. I have a few questions:
(1) Has anyone figured out why object gets stuck even if external timeout is set? Any workaround suggestions?
(2) Is there a way to get an alert or query when a process is showing at a "Warning" State?
------------------------------
Ejaj Meemo
RPA Developer
BT
Europe/London
------------------------------