I assume it is query timeout exception. This service is rather resource intensive and in order to avoid very long running requests there is a query timeout after some seconds.
In case of a timeout you get the following json result:
Yea, it appears to be a timeout exception. it's not as bad today, but still happens every now & then. is there any solution to this problem? seems like installing the database on my own server might solve it, right?