# Handling Errors in Perspective

**URL:** <https://forum.inductiveautomation.com/t/handling-errors-in-perspective/45671>\
**Category:** Ignition\
**Tags:** scripting, perspective\
**Created:** [April 16, 2021, 3:07am UTC](https://forum.inductiveautomation.com/t/handling-errors-in-perspective/45671 "2021-04-16T03:07:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 9, 2023, 8:15pm UTC](https://forum.inductiveautomation.com/t/handling-errors-in-perspective/45671/5 "2023-01-09T20:15:22Z")

</div>

Jython's bare `except` won't catch Java exceptions, for complicated reasons. You must add an additional catch clause:

> [@system.db.runUpdateQuery Exception Handling](https://forum.inductiveautomation.com/t/system-db-runupdatequery-exception-handling/68237/2):
>
> Normal jython try: -- except: won't trap java exceptions. You often need two except: clauses, the first being except java.lang.Throwable, t: or similar. Some [related discussions](https://forum.inductiveautomation.com/search?q=Throwable%20%40pturmel). Note that when catching such exceptions in Vision Client scope or Designer scope, the real SQL exception is not available--it won't serialize and the JDBC classes don't exist in those scopes anyways.

---

_[View the full topic](https://forum.inductiveautomation.com/t/handling-errors-in-perspective/45671)._