If the detailed revenue data (select Goals from the main menu, select a goal, click on the sparkline with "XXXX overall revenue" written after it) has large enough numbers, they will be sent in scientific notation, and the parser will throw up this message and fail to load:
JSON Parse Error [Bad Object] Error at character 3927, line 80:
We ran into a similar problem in #839 and reported it upstream to the OFC dev. (The workaround was to cast to int ... which is ok for ranges.)
Perhaps we can fix this in our fork of OFC?
Maybe we can merge up with the "community release" at http://code.google.com/p/ofc-etw (appears to have the blessing of the original OFC dev).
This is the relevant OFC-ETW bug: #24 JSON parse error for scientfic notation
The bug in OFC is that it generally can't parse scientific notation. Something small like 1.0+e01 would trigger the error. IIRC we worked around something similar (prior to the OFC-etw fork).
I'm also vaguely recalling a bug with locales and commas. It would be nice to have at least this ticket or #1882 open as a reminder for further investigation.