# system.db.runUpdateQuery Exception Handling

**URL:** <https://forum.inductiveautomation.com/t/system-db-runupdatequery-exception-handling/68237>\
**Category:** Ignition\
**Created:** [January 4, 2023, 10:20pm UTC](https://forum.inductiveautomation.com/t/system-db-runupdatequery-exception-handling/68237 "2023-01-04T22:20:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 4, 2023, 11:08pm UTC](https://forum.inductiveautomation.com/t/system-db-runupdatequery-exception-handling/68237/2 "2023-01-04T23:08:44Z")

</div>

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/system-db-runupdatequery-exception-handling/68237)._