Part of the query on sys_user has been ignored because of insufficient access for 'query_range'

[RobDoyle]

Part of the query on sys_user has been ignored because of insufficient access for 'query_range' operation on sys_user_grmember.user

So we recently got our May security maintenance done and I am having an issue with the above error 

I have created a new ACL for this but it is still erroring I did raise a ticket but wasn't very helpful and the KB's don't really advise how to resolve this 

I am not sure what I am doing wrong I did have one related to a query match which i resolved but this query range one is stumping me 

[dwtaber]

Is the query_range operation a superset of query_match? In other words, if I create a query_range ACL for a field, will a user who meets its criteria also be able to use the operations covered by query_match, or do I have to make a separate ACL for those operations?

[Rogers Cadenhe1]

It is not a superset. The query_match ACL checks whether a user has read access to all fields used in a query. You likely need ACLs of both operations to fix errors users are now seeing.

[Krish23]

Any solution for this? we are seeing the same in our instances.

[Rogers Cadenhe1]

Try this:

https://www.servicenow.com/community/developer-forum/part-of-the-query-on-sys-user-has-been-ignored-...

[RobDoyle]

Just to mention that it is only affecting App Engine Licensed users ITIL users are not affected