A few times it's happened where I've been trying to tie together a Fact Table SQL query and it seems to lag a bit, but doesn't change anything in the UI, but then we look at our Postgres CPU and it is pinned to 99%. It would be great to figure out how to implement some sort of catch or timeout for the query process so we're not unknowingly killing our database with no information from the GB side.