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

Description

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

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