---
sourceDocument: Yokohama Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/now-intelligence

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# KPI Signals automated detection jobs

# KPI Signals automated detection jobs {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The KPI Signals application includes jobs that detect signals
automatically. These jobs run so responsible users can be notified of new signals without opening
the application. The job for signals on formula indicators requires scheduling.

When you view an indicator in KPI Details and open the KPI Signals panel, that indicator is checked for signals. You therefore always have the most up-to-date
signals. However, the KPI Signals application also has automated signal detection
jobs. These jobs send notifications about signals to subscribed users without them having the
application open.

For [automated indicators](https://www.servicenow.com/docs/ZaIJQWV6_9ZI1JkGkx2LHA#gloss-automated-indicator "An automated indicator uses an indicator source as its data set. The indicator source specifies a table or database view, conditions for filtering records from that source, and the frequency at which you expect to display the data. The indicator applies an aggregator and optional conditions to this data. The indicator also specifies a data collection job and any breakdowns to apply."), these jobs run whenever a [data collection job](https://www.servicenow.com/docs/ZaIJQWV6_9ZI1JkGkx2LHA#gloss-data-collector "A scheduled job that collects data from one or more indicator sources to produce indicator scores.") runs. The KPI Signals application checks all indicator and [breakdown element](https://www.servicenow.com/docs/ZaIJQWV6_9ZI1JkGkx2LHA#gloss-breakdown-element "The values for a breakdown. For example, the Priority breakdown may have the elements Critical, High, and Low.") combinations that it is active for. The data collection jobs are domain specific, so the signals are also domain specific.

The situation is different for [formula indicators](https://www.servicenow.com/docs/ZaIJQWV6_9ZI1JkGkx2LHA#gloss-formula-indicator "Produces a computed indicator score from one or more other indicators. Besides indicator scores, the formula can include calculations such as the gap between an indicator score and the indicator target."). The formula in a formula indicator uses the scores of other indicators. These other indicators are referred to as [contributing indicators](https://www.servicenow.com/docs/ZaIJQWV6_9ZI1JkGkx2LHA#contributing-indicator "An indicator that is used in the formula of a formula indicator. A contributing indicator can be an automated or a formula indicator."). The scores of these indicators can be collected in different data collection jobs. Bear in mind the KPI Signals calculation uses the most recently detected contributing indicator scores. The KPI Signals job should run after the scores of all the contributing indicators have been detected.

To help you ensure that formula indicators are checked for signals at the right time, the KPI Signals application comes with a scheduled job: PA - KPI Signals - Formula Indicator Signals Calculation Job. This job has a default setting to run every 8 hours, but you have the possibility to optimize this
timing.

## Schedule the job to detect signals for formula indicators {#ariaid-title2}

Set the PA - KPI Signals - Formula Indicator Signals Calculation Job to run after all
data detection jobs have run.

### Before you begin

Review the Performance Analytics data detection jobs. Determine a time after these jobs have run that signals should be detected for formula indicators.  
Note:  
This procedure is optional. Modifying the job schedule can prevent lags between new scores and new signals on formula indicators. However, the default signal detection every 8 hours should not produce errors and may be sufficient for you.

Role required:
admin.

### Procedure

1. Navigate to AllSystem DefinitionScheduled Jobs.
2. Filter the list for jobs whose name contains <kbd class="ph userinput">KPI Signals</kbd>.
3. Open the PA - KPI Signals - Formula Indicator Signals Calculation Job.
4. Modify the following fields to schedule the job:  
   {#schedule-job-signals-formulas__table_lhw_wbc_5mb__entry__2}

   | Field | Description |
   |-|-|
   | Run | Frequency you want the job to run. The choice of subsequent fields depends on your setting in this field. By default, the job runs Periodically. |
   | Day | Day you want the scheduled job to run. If you selected Weekly in the Run field, this field displays the days of the week. If you selected Monthly in the Run field, this field displays the days of the month. |
   | Time | Time you want the scheduled job to start. |
   | Repeat Interval | Number of days and hours before the scheduled job runs again. This field appears when Periodically is selected from the Run list. By default, the job runs every 8 hours. |
   | Starting | Date and time to start the periodic updates. This field appears when Periodically is selected from the Run list. |
   [ ]

   {#schedule-job-signals-formulas__table_lhw_wbc_5mb}

*[\>]: and then