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¶ms=%7B"user"%3Anull%7D
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.
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.