# Build 896 - Private messages don't include enough context
**URL:** https://www.finalbuilder.com/forums/t/build-896-private-messages-dont-include-enough-context/5742
**Category:** Bugs
**Created:** [September 26, 2012, 2:27am UTC](https://www.finalbuilder.com/forums/t/build-896-private-messages-dont-include-enough-context/5742 "2012-09-26T02:27:03Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 26, 2012, 2:27am UTC](https://www.finalbuilder.com/forums/t/build-896-private-messages-dont-include-enough-context/5742/1 "2012-09-26T02:27:03Z")
When exceptions occur, I'm interested in the **Project, Configuration, Stage** that triggered the exception, so I know what I've stuffed up. If you have a look at the following Error I've got [buckleys](http://en.wiktionary.org/wiki/Appendix_talk:Australian_English_vocabulary) chance of finding out where in my 16 Continua project configurations I've got a problem. It also makes it hard for me to trace back any settings during testing.
In this case it's a fairly scary security warning, that I really want to know about.
---
### Author:  [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 27, 2012, 12:08pm UTC](https://www.finalbuilder.com/forums/t/build-896-private-messages-dont-include-enough-context/5742/2 "2012-09-27T12:08:35Z")
It looks like core\_event table is missing **sourcentityid, sourceentitytypeid** and **sourceentityname** data from the exception handler that's configured. It would make exceptions much easier to follow up if this information was retained and used in messaging/notifications etc.
[Continua\_896\_ExceptionLog.zip](https://www.finalbuilder.com/forums/uploads/default/original/2X/1/1575464cc98827f44cb326a33e87ef97e8a8c1ee.zip) (8.491 KB)
---
### Author:  [@vinnie](https://www.finalbuilder.com/forums/u/vinnie)
#### Post date: [September 28, 2012, 3:59am UTC](https://www.finalbuilder.com/forums/t/build-896-private-messages-dont-include-enough-context/5742/3 "2012-09-28T03:59:37Z")
We fixed this bug yesterday and is in build 902. The problem was our GET request was returning JSON unintentionally. We made some changes so the GET request followed the correct path where a page is returned rather than JSON.
As for the stack trace giving you nothing to go off… it was worse for us, trust me hehe. There’s really not too much we can do in the situation that happened here… it was in the depths of MVC code. We’ll look into more logging but it’s a guess at what to log. In this situation there was nothing you could do other than report it.