Hey guys,
just started getting this error on my cloud version, not having this issue on self-hosted instance, and also didn't have that issue last week. Think its a retool bug.
Chiming in to validate that this happened to us yesterday. Issue was transient and things seem to have returned to normal, but this was a real thing on Cloud.
Thanks for reaching out! Can you confirm that your queries are back to running normally, @FlipEngine? I'll look into that specific release and track down potential causes.