"invalid table name: open_nlu_predict_state_tracking" errors since upgrading to Quebec

Hans Peter
Tera Contributor

Hi,

Since we upgraded our instaces to Quebec, we're getting the following error around every minute (loglevel "Warning"):

org.mozilla.javascript.EvaluatorException: GlideRecord.addQuery() - invalid table name: open_nlu_predict_state_tracking (<refname>; line 7)
Line(7)
staleVAPredictionStateGR.addQuery('app', 'Virtual Agent');
evaluateString(JavaScript evaluation error on:
var VA_NLU_PREDICTION_TIMEOUT = parseInt(gs.getProperty('com.glide.cs.nlu.predict.timeout') || 30); // seconds

var timeoutThreshold = new GlideDateTime();
timeoutThreshold.add(-(VA_NLU_PREDICTION_TIMEOUT * 1000));

var staleVAPredictionStateGR = new GlideRecord('open_nlu_predict_state_tracking');
staleVAPredictionStateGR.addQuery('state', 'NOT IN', 'COMPLETED,CANCELLED,TIMED_OUT,SERVICE_ERROR,PREDICT_ERROR');
staleVAPredictionStateGR.addQuery('app', 'Virtual Agent');
staleVAPredictionStateGR.addQuery('app_document_table', 'sys_cs_conversation_task');
staleVAPredictionStateGR.addQuery('mode', 'ASYNC');
staleVAPredictionStateGR.addQuery('sent_on', '<=', timeoutThreshold);
staleVAPredictionStateGR.query();
var timeoutCandidates = [];
while (staleVAPredictionStateGR.next()) {
if ('suspended' == staleVAPredictionStateGR.app_document.getRefRecord().state) {
var stateTrackingSysId = '' + staleVAPredictionStateGR.getUniqueValue();
var convSysId = '' + staleVAPredictionStateGR.app_document.getRefRecord().conversation;
var csTaskSysId = '' + staleVAPredictionStateGR.app_document;
var userSysId = '' + staleVAPredictionStateGR.user_id;
sn_cs.VASystemObject.timeoutNLUPrediction(convSysId, csTaskSysId, stateTrackingSysId, userSysId);
}
}
)

 

I can't really find a business rule or script include that contains these lines of code, but it seems to be about Virtual Agent and NLU, which we're currently not using at all. 

It kind of looks like I'm missing a plugin or something, but I'm a little surprised since we're not using VA / NLU features at all, and I honestly don't even know our license situation in regards to those applications. Did anyone else have this problem after upgrading to Quebec?

Thanks in Advance for your help,

Hans

1 ACCEPTED SOLUTION

Hi Hans,

Quick follow up. I have logged a support case for this and have the following information back.

This is related to PRB1498255 - Timeout For VA Chats Suspended on NLU Prediction script cluttering logs. 

This scheduled script was installed during the Quebec upgrade which references a table installed by the "Proxy agent for connecting to Natural Language Understanding (NLU) providers" plugin.

The defect is permanently fixed in Rome release. The suggested fix is to modify the script to the Rome fixed version by adding a condition to the scheduled script:

Approach to modify the scheduled script in following steps:

  1. Go to the scheduled script 'Timeout For VA Chats Suspended on NLU Prediction'
  2. Click the Conditional Check box and the Condition window will be displayed.
  3. Enter the condition: new GlidePluginManager().isActive('com.glide.nlu.proxy') && gs.tableExists('open_nlu_predict_state_tracking');
  4. Save the change

If all else fails after this would probably suggest you log your own support case with NOW Support.

Kind Regards,
Shane

View solution in original post

6 REPLIES 6

Hi @Shane Butler 

Thanks for providing this. I had a similar scenario: brand new customer with CSM, we turned off the agent chat for their CSM portal at this time. This may or may not have contributed to this "Warning" showing in the logs every 30 seconds (that's how often this scheduled script is set to run: Timeout For VA Chats Suspended on NLU PredictionTimeout For VA Chats Suspended on NLU Prediction).

After adding the conditional check with what you've posted, this has stopped the error from showing. They're still on Quebec.

Thanks again!

-Allen


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

bvlo
Tera Expert

Hans,

We are seeing this issue as well. It appears to be coming from a scheduled job called: Timeout For VA Chats Suspended on NLU Prediction. Which appears to be written by ServiceNow. Any chance you have additional details since posting this? I might open a HI case but this does not appear to be effecting anything that we know of.