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.
Logic Error: No Join Found for table: sys_metadata0: no thrown error - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Logic Error: No Join Found for table: sys_metadata0: no thrown error
KB0689688

Logic Error: No Join Found for table: sys_metadata0: no thrown error


2943 Views Last updated : Jul 12, 2025 public Copy Permalink
KB Summary by Now Assist

Description

The error message below may randomly appear in the instance log:

Logic Error: No Join Found for table: sys_metadata0: no thrown error

 

 

In some cases the platform will show it for other tables like "Logic Error: No Join Found for table: <table_name> no thrown error".

Steps to Reproduce

From /sys.scripts.do run;

var gr = new GlideRecord('incident');
var functionBuilder = new GlideDBFunctionBuilder();
var mySubtractFunction = functionBuilder.subtract();
mySubtractFunction = functionBuilder.field('state');
mySubtractFunction = functionBuilder.field('priority');
mySubtractFunction = functionBuilder.build();
gr.addFunction(mySubtractFunction);
gr.chooseWindow(0, 10);

gr.orderBy(mySubtractFunction); //commenting this line will stop the error

gs.print('START');
gr.query();
while(gr.next()){
    gs.print(gr.getValue(mySubtractFunction));
}
gs.print('END');

 

Workaround

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make these decisions lightly, and we apologize for any inconvenience.

The error can be ignored as it is not causing any issues on Customer instances.

 


Related Problem: PRB909359

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.