# Exception codes
**URL:** https://www.finalbuilder.com/forums/t/exception-codes/283
**Category:** Discussion
**Created:** [December 18, 2006, 6:38am UTC](https://www.finalbuilder.com/forums/t/exception-codes/283 "2006-12-18T06:38:38Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@stevage](https://www.finalbuilder.com/forums/u/stevage)
#### Post date: [December 18, 2006, 6:38am UTC](https://www.finalbuilder.com/forums/t/exception-codes/283/1 "2006-12-18T06:38:38Z")
It doesn’t seem possible to get any information about the exception that triggers a catch block. In particular, you can’t distinguish between self-raised (anticipated) exceptions, and unanticipated exceptions. Is this right?The only workaround I have is setting a variable before I raise the exception and testing for that…Steve
---
### Author:  [@tate](https://www.finalbuilder.com/forums/u/tate)
#### Post date: [December 18, 2006, 7:18am UTC](https://www.finalbuilder.com/forums/t/exception-codes/283/2 "2006-12-18T07:18:55Z")
Yes, that’s right - and the workaround you’re using is the right way to handle the situation too.
---
### Author:  [@jhunsaker](https://www.finalbuilder.com/forums/u/jhunsaker)
#### Post date: [July 9, 2007, 10:28am UTC](https://www.finalbuilder.com/forums/t/exception-codes/283/3 "2007-07-09T10:28:56Z")
Hi guys,
Is this still the case? Can one obtain information about the exception natively instead of setting a variable? If not, I'd like to add a vote for the "wish list".
Thanks!
---
### Author:  [@tate](https://www.finalbuilder.com/forums/u/tate)
#### Post date: [July 10, 2007, 3:27am UTC](https://www.finalbuilder.com/forums/t/exception-codes/283/4 "2007-07-10T03:27:01Z")
yes - still the case. I’ll add it to the todo list to enhance the exception handling.