Upon exception, the runtime engine calls an error interception tool that is attached to the runtime engine (e.g., Java virtual machine (JVM)). Based on the nature of the exception, such as its type and the class and method in which it occurred, and based on user preferences, an exception can be either handled or ignored.
If the preference is to handle the exception, then based on handling preferences such as memory search depth, the error interception utility extracts memory values from heap and stack memories. This snapshot then produces the equivalent of a debugger screen (as if there had been a debugger) at the moment of the exception.
This mechanism enables the automated handling of software errors independent of the application source code and of its developers. It is a direct artifact of the runtime engine paradigm and it enables unique advantages to the software life cycle that were unavailable before.
"Getting started with Exception handling". EdgeVerve. 7 February 2024. Retrieved 7 February 2024. https://www.edgeverve.com/assistedge/knowledge-base/RPA19.1/Automation_Studio/Configuring-Automation-Processes/Exception_Handling/Exception_Handling.htm ↩
"Automatic exception handling in conditions". IBM. 2 February 2024. Retrieved 7 February 2024. https://www.ibm.com/docs/en/dbaoc?topic=rules-automatic-exception-handling-in-conditions ↩