Philipp Wassibauer: seemed like it was fixed for a while. now its worse than before and there is a delay or complete pause after clicking run

CryptusChrist: We had pretty big spike of these errors during the rollout of our query execution service last week. Sorry about that.

Since Thursday last week it we resolved one issue on this, which was around large datasets crashing our Graphql services. If you are experiencing this error now then it is very likely due to network connection breaking, triggering this screen. We are working on a fix for that as well. That one shouldn't be a heavy lift and be online relatively quickly.

Can you elaborate on 'there is a delay or complete pause after clicking run'. I just tried it and am not experiencing the same.

Philipp Wassibauer: the clicking run isnt really an issue it just used to 100% the time do something immediately after clicking run. seems like there is a delay for a few seconds now but not really that big of a deal.

CryptusChrist: Got it. I do see a small lag, I will add it to a todo to check what is going on.

We are rolling out another attempt to get rid of most/all occurrences of later today. Will update once we have done it.