In Perspective, I have had trouble with errors not being raised to the user. If I am in a Designer and I execute a button click or something, any errors will pop up in an Error window and print to the console. But if I launch a browser to that page, errors are not raised to be visible to the user. I…

If it’s something you need to alert the user about, I would wrap your logic in a try/except block, and in the exception handling you should use system.perspective.openPopup(). You’ll want to create a View which is able to convey information to the user, whether it the stacktrace or just a warning th…

That sounds simple enough, thank you.

Hi cmallonee , I'm doing as suggested. To the popup window I'm passing the traceback. On a View component def runAction(self, event): try: _.update_db_with_error() except: _.error(self) Script module def error(_self): if _self.session.props.device.type == 'designer': raise params = {'…

Jython's bare except won't catch Java exceptions, for complicated reasons. You must add an additional catch clause: [image] system.db.runUpdateQuery Exception Handling Ignition Normal jython try: -- except: won't trap java exceptions. You often need two except: clauses, t…

Thank you PGriffith Bare except in the code above catches the same error with the same traceback as java.lang.Throwable. If it'll be an any chance to catch "the real SQL" exception in python script, it would be great.

In gateway scope, you get the real SQL exception. Possibly as a chained cause. Those exceptions are not serializable (at least, not without the same JDBC drivers in the receiving scope), so they get summarized in Vision Client scope and Designer Scope.

It seems like it is impossible to get the chained cause (the SQL exception) to the Designer Scope using python. Is there any news from the Ignition dev team on solving this? As a temp fix it would be good to concat the message of the chained cause to the java.lang.Throwable message. We're planning…

It will never be solved, because those classes are only available in the gateway. Consider using a gateway message handler to run your SQL, and that will be able to analyze any exceptions completely. Use system.util.sendRequest() from Vision or Designer scope to run the handler.

[image] Alex_SHARIKOV: We're planning to completely migrate to Perspective Perspective runs in gateway scope, so the complete message should be available there.

What's the best way to catch errors in Perspective? What was I doing wrong in the code above :point_up_2: (4th message from the top) Handling Errors in Perspective - #4 by Alex_SHARIKOV The goal is to catch the entire error message including the SQL cause.

Handling Errors in Perspective

Ignition

paul-griffith January 9, 2023, 8:15pm 5

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