Hi Anthony,

Thanks for checking. Sorry for missing that in the thread.

Short of deleting the container, I don't think there's an alternative way to delete the query through the UI if you're getting that exception.

You can, however, manually delete the row from the database. We normally don't recommend this, of course. It will be stored in the query.querydef table. You can find it based on the "name" (the query name itself) and "schema" columns. You will need to either bounce Tomcat or go to Admin Console->Memory Usage->Clear Caches and GC to un-cache it. Alternatively, you can wait for the cache entry to time out.

Thanks,
Josh