How do I stop a runaway data explorer query?

Hi,

I’m just starting to explore Data Explorer. I plopped in this query: What cool data explorer queries have you come up with? - #196 by SidV

and hit ‘Save Changes and Run’, expecting to be prompted for the parameter value. After waiting a couple minutes, I glanced at my URL and saw to my horror ?id=5&params=%7B"user"%3Anull%7D

So… kill my long-running query?

 
Ann

3 Likes

Good question! I believe we have default query timeout protection in Data Explorer, but someone else from the Discourse team would need to confirm that.

3 Likes

Indeed, we have a 10 second timeout on any queries running via data explorer, so no need to worry about things running for too long :+1:

You should receive some feedback in the UI after that 10s has passed. If not then let us know and we’ll dig into it.

3 Likes

Nope. Nothing. No notifications at all. That’s why I created my post. I was hoping a timeout kicked in, but I had no way of knowing.

3 Likes

Oh, interesting! I just gave it a try here on Meta, and it looked like this: (error at the bottom)

Would you mind trying the broken query one more time on your site, and see whether anything like this appears?

2 Likes

You asked for it! :joy:

3 Likes

Aha! The good news is that the 10s timeout is working correctly on the server-side, so the query did indeed get cancelled. Bad news is that there is some error in the client which is stopping the error from displaying. It seems to be related to the “Null” value for a user, rather than the timeout itself.

We’ll get that fixed up - thanks for reporting!

3 Likes

This will be fixed by

3 Likes

This topic was automatically closed after 17 days. New replies are no longer allowed.