'''Automated Exceptionexception Handlinghandling''' is a [[computing]] term referring to the computerized handling of errors.<ref>{{Cite web |date=7 February 2024 |title=Getting started with Exception handling |url=https://www.edgeverve.com/assistedge/knowledge-base/RPA19.1/Automation_Studio/Configuring-Automation-Processes/Exception_Handling/Exception_Handling.htm |access-date=7 February 2024 |website=EdgeVerve}}</ref> [[Runtime system]]s (engines) such as those for the [[Java (programming language)|Java]] programming language or [[Microsoft .NetNET Framework]] lend themselves to an automated mode of exception or error handling. In these environments, software errors do not 'crash' the [[operating system]] or the [[runtime engine]], but rather generate exceptions.<ref>{{Cite web |date=2 February 2024 |title=Automatic exception handling in conditions |url=https://www.ibm.com/docs/en/dbaoc?topic=rules-automatic-exception-handling-in-conditions |access-date=7 February 2024 |website=IBM}}</ref> Recent advances in these runtime engines enables specialized runtime- engine add-on products to provide automated [[exception handling (programming)|exception handling]] that is independent of the source code and provides root-cause information for every exception of interest.{{Fact|date=July 2007}}
==How it works==
Upon exception, the runtime engine calls an error interception tool that is attached to the runtime engine (e.g., [[JVMJava 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 precise moment of the exception.
== Advantages Effects==
This mechanism enables the automated handling of software errors independent of the application source code of the application and independent of its developers. It is a direct artifact of the runtime engine paradigm and it enables unique advantages to the software lifecyclelife cycle that were not availableunavailable before.
