Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Invalid query detected, please check logs for details [Unknown field undefined in table sc_request] - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Invalid query detected, please check logs for details [Unknown field undefined in table sc_request]
KB0863715

Invalid query detected, please check logs for details [Unknown field undefined in table sc_request]


12922 Views Last updated : Jul 10, 2025 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Multiple messages in the log table or system logs containing the following or similar message:

Invalid query detected, please check logs for details [Unknown field undefined in table sc_request]

Release

Any

Cause

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.


IE: 

 var gr = new GlideRecord('sc_request');
 gr.addQuery('sys_id', current.request);
 gr.query();
 gr.next();  //<----- Problem line



This code should only call a single row, however we attempt to run gr.next(). This will trigger the invalid query error.

Resolution

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. 

Related Links

Review the GlideRecord API for more information

GlideRecord API


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.