query_match issue for workers (m2m_dictionary_dataclass.data_class)

Zach3
Tera Guru

‎05-21-2025 12:41 PM

Related to the recent query_range "May Maintenance" issue...

 

Anyone else seeing lots of query_match issues for system-related 'worker' activity? e.g.:

 

2025-05-20 14:35:16 worker.6 m2m_dictionary_dataclass.data_class query_match

Zach3_0-1747856457824.png

 

I'm unsure if this is actually an issue, and if so, which roles to grant in an ACL to ensure continued system access. Any ideas would be much appreciated!

0 Helpfuls
  • 351 Views
1 REPLY 1

VikMach
Mega Sage

‎05-21-2025 01:39 PM

Hi @Zach3,

Many people reported this and we had an issue with this too.
It is just blocking the query to certain tables and fields where you have not properly configured your ACL's.
ServiceNow has pushed these ACL's to track, manage and maintain access control.
All that you need to do is either create a query_match for the same ACL or simple add roles to the query ACL's created by ServiceNow.
How to find which role to add? - Open those query_range ACL's and you will see in the description where those ACL's are copied from (sysID of the original ACL's are mentioned). Those same roles need to be added to the new query_range ACL's. Navigate to that ACL which query_range ACL's are pointing at and take note of those roles and add to new query_match ACL's. We did the same in our environment and it solved the issue. Same is also suggested in the KB I mentioned below.
See similar issues reported by others and solution proposed by ServiceNow.
https://www.servicenow.com/community/developer-forum/query-range-acl/td-p/3265154/page/2

Additionally following KB gives complete understanding of why and what kind of stuff. (You need to have Hi support access to read this KB)
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2130442

 

Let me know if this helped.

Regards,
Vikas K

0 Helpfuls