# Handling Exceptions **URL:** \ **Category:** Ignition\ **Created:** [September 10, 2015, 5:44pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449 "2015-09-10T17:44:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![oscar.salcedo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/oscar.salcedo/32/11019_2.png) [@oscar.salcedo](https://forum.inductiveautomation.com/u/oscar.salcedo)\ **Post date:** [September 10, 2015, 5:44pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/1 "2015-09-10T17:44:59Z")
Hi, Is there a setting to hide all exceptions across a project? We have some unattended displays that show data on the floor shop and we would like all exceptions to be ignored; we have try-catches around all major functions calls and methods, but when something outside of those fails, the exception is visible on the screen and the users can’t see some of the screen content. Any ideas? Thanks! Oscar Salcedo ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [September 11, 2015, 4:11pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/2 "2015-09-11T16:11:17Z")
What type of exceptions, is it a custom property on a windows, a tag, or component? Can you post an example or two? I am not aware of a global hide of errors but you can always hide them with code ---
**Author:** ![oscar.salcedo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/oscar.salcedo/32/11019_2.png) [@oscar.salcedo](https://forum.inductiveautomation.com/u/oscar.salcedo)\ **Post date:** [September 14, 2015, 3:02pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/3 "2015-09-14T15:02:53Z")
Any and all exceptions; any that will show an error message on the screen that would have to be cleared/acknowledged by someone. These screens are unattended and nobody has access to them hence the error message would be on top of the data being displayed. I hope that helps clarify. Thanks! Oscar Salcedo. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [September 14, 2015, 3:13pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/4 "2015-09-14T15:13:29Z")
There’s not one, as far as I know, but again, it really depends on what is actually happening. But if you can give us an example what exceptions you are seeing, we may be able to get to the root of your problem. Also, you can use something like TightVNC to remotely get to the PCs running the displays, if you’re not already doing this. ---
**Author:** ![oscar.salcedo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/oscar.salcedo/32/11019_2.png) [@oscar.salcedo](https://forum.inductiveautomation.com/u/oscar.salcedo)\ **Post date:** [September 14, 2015, 3:21pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/5 "2015-09-14T15:21:40Z")
See attachment - this is one of those that I can put try-catches around, but you get the idea of what type of error messages I am talking about. We are not using VNC yet but plan on it. Thanks again! Oscar. ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/1/1756bb5e7af00463f6df2f225e865cd2354ff2c7.png) ---
**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\ **Post date:** [September 14, 2015, 8:23pm UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/6 "2015-09-14T20:23:10Z")
Can I risk being simplistic and say this is what testing is for?! You test your system and catch as many of these errors as you can and fix them. You then repeat until the system is solid - although perfection is impossible you shouldn’t be putting out any system that regularly brings up error dialogues. ---
**Author:** ![ian](https://avatars.discourse-cdn.com/v4/letter/i/bb73d2/32.png) [@ian](https://forum.inductiveautomation.com/u/ian)\ **Post date:** [September 15, 2015, 8:43am UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/7 "2015-09-15T08:43:22Z")
Hi oscar.salcedo, This may sound counter-intuitive, but if what you mean is the one that you show in the example, you should put try-except block in the script which cause the error window to occur to remove the error window. something like: `try: #something causes error window to appear here! except: a = 0 #just do anything non-harmful here ` This will make the error window disappear because Ignition would think that you aware of the error and has created proper try-catch block for it. That is how you can remove the error window. However, as AlThePal has stated, actually the error window is meant for us to find bugs and to solifidy our system. Making it disappear may not really get rid of the actual issue. Hope that will help. ---
**Author:** ![ian](https://avatars.discourse-cdn.com/v4/letter/i/bb73d2/32.png) [@ian](https://forum.inductiveautomation.com/u/ian)\ **Post date:** [September 15, 2015, 8:50am UTC](https://forum.inductiveautomation.com/t/handling-exceptions/10449/8 "2015-09-15T08:50:46Z")
> [@](#): > > has created proper try-catch block for it I meant "try-except" block. Also, the "details" tab screenshot as well as your script from your example (instead of the "message" tab screenshot) from your example may be useful (since probably there is no way to disable the exception globally)