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

RobDoyle
Giga Guru

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 

RobDoyle_0-1747150176095.pngRobDoyle_1-1747150202045.png

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 

1 ACCEPTED SOLUTION

RobDoyle
Giga Guru

RobDoyle_0-1747219362432.png

So it appears me updating these ACL's to change from public and also changing the security attribute to local seems to have fixed the error 

View solution in original post

17 REPLIES 17

MatteoMazz
Tera Contributor

Hi, I'm experiencing the same issue in my instance when viewing reports that contain custom fields. The query range ACL includes the scrum_user role, which most users have, but the reports still aren't displayed

@MatteoMazz have you tried to set the security attributes to local and seen if that fixes it 

SreedharPasupul
Tera Contributor

It seems there is an article out there where they have explained the Securty patch. Hope this may help people who faces the issue.

https://www.ikconsulting.com/post/understanding-servicenow-s-may-2025-query-range-acl-update-what-yo...