Clarification on Indicator Source Frequency vs Indicator Job Frequency in Performance Analytics

[rubesh_u]

I have a question regarding how frequency works in Performance Analytics.

In my setup:

 - The Indicator Source has Valid for frequency = Daily

 - The Indicator Job is configured to run Hourly

I want to understand how these two settings interact. From my understanding:

  - The Indicator Source restricts the indicator to be Daily

  - The Indicator Job runs every hour and updates the value

My questions are:

1.Does the hourly job overwrite the same daily score multiple times throughout the day?

2.Will only the latest value of the day be stored?

[Naveen20]

How frequency and job scheduling work together:

The "Valid for frequency" on the Indicator Source determines the granularity of score storage — meaning how scores are bucketed in time. When it's set to Daily, PA stores one score per day for that indicator. The Indicator Job's schedule simply controls how often the computation runs.

To your specific questions:

1. Yes, the hourly job overwrites the same daily score throughout the day. Each time the job fires, PA recalculates the indicator and writes the result to the current day's score slot. Since the frequency is Daily, there's only one slot for today — so each hourly run replaces the previous value for that day.

2. Yes, effectively only the last computed value persists as the day's score. There isn't a history of the intra-day overwrites. Once the day rolls over, whatever value was written last becomes that day's final historical score, and a new slot opens for the next day.

Why this pattern is useful:

Running the job more frequently than the storage frequency makes sense when you want the current day's score to stay relatively fresh throughout the day (for dashboards, widgets, etc.) rather than waiting for a single end-of-day run. The tradeoff is extra computation for more up-to-date reporting during the day.

One thing to watch: If your indicator uses a collect-based source (as opposed to a formula), each hourly run queries the underlying table again, so the score naturally reflects the latest state of records at that point in time. Just be mindful of the performance cost if you have many indicators on hourly jobs — that's the main reason ServiceNow defaults most sources to Daily.