Hello jackh, We met the same exception and tried to debug the javascript that handles the parsing of the actual content that returns from the server. We noted that there is a bug/problem within the parser logic that parses incorrectly one of the update blocks. You can see the bug if you look in the WebResource...