I agree, not very helpful in terms of troubleshooting the issue but we are working on better error reporting.

If you are ever able to get a reproducible testcase/set of JSON please let us know so we can test it. That being said I dont think the error is with noCache; just with the server-side JSON that was being generated.