We get this request a lot, and we're still thinking through what the right user experience should look like for this. Another usecase for this we hear about is if you have a very large app with several queries so the initial load takes forever, but all you wanted to do is go in and change one small thing.
Feel free to expand on the topic here, or with me in a DM – we're happy to take your use case into account as we design the right user experience for this.
old request but wanted to throw my support behind it as well! I just had to deal with a module choking on queries running with no data...just so i could finally change them not to run on no data. crashed my browser twice before I could make the changes
I feel like this should be an important feature. I'm currently stuck in a situation where a broken query kicks me off the page its on, so I can't edit it, as trying to open the query (either by navigating to the page, selecting the page in the queries side menu, or even opening it through global search) will also navigate the page, which in turn triggers the query, which kicks me off the page, making it impossible to edit the query to fix it.
Hi @NathanTew. This is a high priority feature for us and I added your +1 to the FR. For now, to fix your specific type of issue you either need to use the version history or a last resort would be directly editing the app json like mentioned in this thread, to remove the broken query.