I can't say for sure you are encountering the same root issue, but we did fix a bug in EG 7.1 with a similar symptom.  I think there is a reasonable likelihood the problem you are seeing is caused by the same root issue, which was addressed in EG 7.1.   I'm not aware of any workarounds in EG 6.1.  The unexpected error leads to the query being in an unexpected state, which is not handled gracefully when deserialized. ... View more