Historical & Daily Jobs

PaulSylo
Tera Sage
Tera Sage

Hi All,

Can someone help me to understand do we need this "historical job" running on a daily basis? If so, why do we need to run this on a daily? sounds very basic, but still help me to get out of assumption out of my mind.

Regards,

Paul

Regards,
PaulSylo

Kindly mark "helpful", if this helps, or Mark as "Accepted " if it solves your issues !
1 ACCEPTED SOLUTION

@Paul Sylo  yes we can do this as for the first time it will collect the entire data for the records which were there before PA was set ! 

After that based up on your requirement you can have it or remove it depending on the clients ask

please mark my answer correct if it helped you

View solution in original post

9 REPLIES 9

@Paul Sylo  yes we can do this as for the first time it will collect the entire data for the records which were there before PA was set ! 

After that based up on your requirement you can have it or remove it depending on the clients ask

please mark my answer correct if it helped you

Thanks a Ton! Mohith

Regards,
PaulSylo

Kindly mark "helpful", if this helps, or Mark as "Accepted " if it solves your issues !

Community Alums
Not applicable

Hi @Paul Sylo ,

You have marked your own answer as correct by mistake, Please mark the right answer as correct 🙂

Thanks,

Sandeep

Dipu Joy
ServiceNow Employee
ServiceNow Employee

Historical Jobs should be run only once when your organization conceives the PA for that module and it should be kept On Demand.

Once this is completed, Daily jobs will take over as it runs daily.

Historical jobs should never be executed again as it will overwrite the historical data collection with a new Snapshot when it executes again.

We have had DataLoss issues raised by customers where OLD Snapshots were lost because of executing the Historical jobs again which will mess up the whole reporting for all historical timelines.

 

So use Historical Job execution with caution once that module is live.

Thank you