Email summary - Invalid query detected, please check logs for details [Unknown field role_override i

Mira1992
Kilo Sage

Hello,
whan I'm trying to create and execute the Scheduled Email Summary (sysauto_indicator_notification) it does not send anything.

Mira1992_1-1710313329923.png

 


In the syslog table I can see the following:
Invalid query detected, please check logs for details [Unknown field role_override in table sysauto_indicator_notifications]

Mira1992_0-1710313169510.png
The same setting works just fine on my PDI.
I've checked all the BR containing the role_override but it all seems to be fine (I also tried to deactivate it and still no success).
Would you know what might be the issue?
Thanks a lot!

 

1 ACCEPTED SOLUTION

Mira1992
Kilo Sage

Hello,
the warning was not caused by any BR but it was much more simple.
Email notification which should have been triggered by the Email summary was set as inactive so all I had to do was to set it active.

View solution in original post

2 REPLIES 2

Sohail Khilji
Kilo Patron
Kilo Patron

Hi @Mira1992,

 

Here is the solution given in KB : 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0863715

This error is produced by a business rule on the affected table (Usually that table is part of the error message IE: sc_request). 

 

The business rule will attempt to call the GlideRecord function next() on a GlideRecord object, when that object has no more records to return on the list.

 

Be careful when using gr.next() on a GlideRecord object. Usually these are part of a conditional statement such as a while loop or an if otherwise it would be a similar equivalent to an out of bounds error in an array. 

Simply avoid using gr.next() outside of conditional statements if not needed to loop through one or more records. If only returning one record and the unique sys_id is know, please use the gr.get('REPLACE-SYS-ID-HERE') function. 


☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....

LinkedIn - Lets Connect

Mira1992
Kilo Sage

Hello,
the warning was not caused by any BR but it was much more simple.
Email notification which should have been triggered by the Email summary was set as inactive so all I had to do was to set it active.