skip to Main Content

When I use the "New Query" option on Azure Resource Graph Explorer page, the "Run Query" button is disabled.
When I use a sample query it is enabled and works, but when I update the query with any changes, I can run it but it keeps showing the result from the original query that I had opened. Seems like the result is caches or something.

Any ideas if this is a bug on the Azure portal or what?

3

Answers


  1. When I use the "New Query" option on Azure Resource Graph Explorer page, the "Run Query" button is disabled.

    Yes, It is disabled at first as there is nothing to run or execute like below:

    enter image description here

    Then when I enter a character like below and run query is enabled as below:

    enter image description here

    Ran sample query as below:

    enter image description here

    then my query:

    enter image description here

    You can see it has changed, If you are seeing same results then I guess then the results of both queries are same even after filtering or producing same outputs.

    Now trying with saving a query:

    enter image description here

    Sometimes, when you are saving it, it does not save immediately:

    enter image description here

    Its still showing previous saved results(as the results are not saved even after saving):

    enter image description here

    You need to click on Save or Ctrl S for 2 or 3 times then it will be saved:

    enter image description here

    This is a expected behavior in Azure Resource Graph Explorer.

    Login or Signup to reply.
  2. Thank you for taking your time to answer me with very clear screenshots.

    That is precisely where I’m stuck with the issue.

    First/second/third screenshot : I’m ok with
    Fourth screenshot : whatever the query I try to personalise. For instance :

    Resources
    | project name, type, location
    | order by name asc

    the ‘Run query’ runs the previous query (resources) with all the columns and not only on the name, type, location. It’s like it uses a cache.

    Spent a couple of time to find out a workarround but not successfull yet.
    If any idea I’ll take it because for now I’m stuck.

    Login or Signup to reply.
  3. Just want to share with you the latest status of the issue and it’s not very glorious 🙂

    The issue ix fixed just by empying the web browser cache or by using an Incognito session of the brower.

    Hope it can help if you are experiencing the same issue.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search