Apologies for the delay here! If you go to the query builder and do a query that has the same scope, eg asset.sites IN [‘scg’], do you see the correct number of assets listed there?
And under the “Build Goal” section of your goal where you configure the type, did you select “Remediate vulnerabilities” or “Configure assets”? What do your queries look like there? That should make this a little easier to understand.
Yes, if I use the scope in the query builder I get the correct number of assets.
In the “Build Goal” section I select “Configure assets”. It´s also shows the correct number of assets there, but after deploying the Goal, the number gets wonky.
Thanks for the patience here. I’ve confirmed with a team member that your setup with the scope + condition you shared looks correct. One question - did your team change consoles around early to mid January? I ask because when we took a look at this on the backend, it looked like there might be extra assets included here that are potentially from an “old” console. That could explain the larger numbers and provide a path forward for clearing those assets and getting the correct number in this goal.
So in this case, to double check the console status and get to the bottom of the goals issue you’re seeing, I think it would be best to open a ticket with our Support team. They’ll be able to get a better look into your environment than we can here on the forum and help figure out why you’re seeing those extra assets. They can also determine if there were indeed any changes regarding your console that could be contributing to this.