---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Spotlight job logs

# Spotlight job logs {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The steps of Spotlight jobs are recorded in logs. Use these logs to debug any issues.{#spotlight-logs__ph_spotlight-logs}

Users with the pa_spotlight or admin roles can read and delete Spotlight job logs.

The logs are listed at the following locations:

* At SpotlightSpotlight Logs.
* As the Spotlight Job Logs related list on the relevant Spotlight Group record.

{#spotlight-logs__ul_plf_jly_kcb}

The same Spotlight Job Logs list opens in both places, but in the Spotlight Group form, the
list is filtered by that Spotlight group.

To debug a Spotlight job, open the job log from the list and examine the job log row fields.  

## Debugging Spotlight jobs

Consider the Incident Spotlight group, which evaluates real-time data from the Incident
\[incident\] table. This table is the table that the indicator source of the Number of open
incidents indicator uses. A Spotlight job runs on this Spotlight group every day at 15:00 hours.

The Spotlight jobs for this group generate the following list of Spotlight job logs, where the
most recent job completed with errors:  
Figure 1. Spotlight job logs

Clicking the timestamp of the 04:02:03 job shows a successful job with only informational
messages.

Returning to the list and opening the log for the job that had errors, you see that the
Spotlight criterion Incident more than 30 days old is invalid.

Navigating to the Spotlight criteria, you see that Incident more than 30 days old is an indicator-based criterion that uses the Age breakdown.

Viewing the Age breakdown shows that it uses a script in a breakdown mapping.  
As shown at the top, the Incident Spotlight group evaluates real-time data. Therefore, the group cannot support criteria that use scripted breakdowns. For the job to run without errors, replace this criterion with a criterion that uses a query instead of an indicator and a breakdown. For example, create a criterion that queries the Incident \[incident\] table with the following conditions:

* \[\[Opened\]\[relative\]\[on or before\]\[30\]\[Days\]\[ago\]\]
* \[\[Opened\]\[relative\]\[on or after\]\[90\]\[Days\]\[ago\]\]
{#spotlight-logs__ul_rjn_x5r_kfb}

For more information, see [Create Spotlight criteria](https://servicenow-prod.fluidtopics.net/OyDg4blckjVdjwUu4Ndkeg "Create Spotlight criteria to define when to weight a record, and the weight to assign.").

*[\>]: and then