In this example, there is a Divide 1 by 0 action that generates a caught exception.
Prior to the execution of the function, Before exception occurs is written to the log. After the execution of the function, After exception occurs is written to the log.
Processing of the actions continues and is not impacted by this caught exception.
The LibraryObjects logger log level must be set to INFO or above
When this rule turns on:
| 1. | Before exception occurs is written to the log. |
| 2. | When the Divide function executes it throws a caught exception and writes an error to the log automatically. |
| 3. | The processing continues and After exception occurs is written to the log. |
