System log errors: [RemoteTable] VScriptableTableData: Unable to resolve javascript condition

[chuckn]

We've been investigating high count system log errors in our environment and this one has us perplexed. We engaged Now Support for an assist, but that didn't lead anywhere.

We get about 1200 errors similar to this every day (the dates change):

[RemoteTable] VScriptableTableData: Unable to resolve javascript condition expression: javascript:gs.dateGenerate('2023-09-19','start')@javascript:gs.dateGenerate('2023-12-18','end'): no thrown error

Looking at one of those errors, the context is:

{"_system_id":"*.service-now.com:moog025","caller":"com.glide.schedule_v2.SchedulerWorkerThread","_logged_in_user":"system","job_name":"Update Search Analytics Data","record_sys_id":"336e37f25b7c6910d9a5ce1a8581c7d3","_user":"system","_is_impersonating":"false","table_name":"sys_trigger","_session_id":"glide.scheduler.worker.4","_txid":"89965abb4303"}

That Scheduled job is just:

var utils = new SearchAnalyticsPrecalculatedData();
utils.populateData();

So looking at populateData() in SearchAnalyticsPrecalculatedData(), it references the 

sn_ais_admin_tools_ai_search_analytics_dashboard_precalculated_data table, which is full of records created/updated by admin or system (in other words, nothing we've touched as a customer). I suspect one of the Encoded queries in one of those records is an issue, but nothing's jumping out to me.

Has anyone seen a similar issue and figured out the cause?

Thanks!

-Chuck

[Community Alums]

I had similar issue(problem to be frank,but lets politically appropriate ;)). Soo AIS is attemping to get as much as possible data even if non existing one. That was 2021 and support and R&D actually told me its bad config so iended disabling several AIS related jobs + system properties. Cant remember exactly which but surely you can find them. Hope this will give a clue

[chuckn]

Thanks so much for your reply, Joro! Did you disable those jobs and properties because you did not want to us AI Search? I would be open to disabling them but we do use AI Search and I wouldn't want to cause it to break.

Perhaps I'll open another Support case specifically with the AI Search team.

[Mark Roethof]

Nice one!

Coincidently I logged a story on our backlog for this system log error, I noticed that happens daily thousands of times. Not picked up yet, so can't contribute here yet. Though will follow this 🙂

[chuckn]

Per Now Support, there's a known problem causing these logging messages: PRB1708878. The only details are: Getting "com.glide.script.RhinoEcmaError: missing ; before statement" after upgrading to Utah P2 or above when "Update Search Analytics Data" job runs. The PRB was opened in October and the plan is to resolve this issue in the next update to Advanced AI Search Management Tools (currently planned around May 2024).

So...good to know it's actually not something we did as the customer!