Error on PA Job: Clearing the flushed snapshots for job run... (HELP)

[Farrah1]

When running a PA Data Collector job, can anyone tell me what this error means (and what to do about it)?

Error collecting for 20220210. Clearing the flushed snapshots for job run with log sys_id 295def2287a50d14303fe58e0ebb3585 java.lang.IllegalStateException: Sparse storage format has one field, sys_id
at com.glide.db.meta.SparseStorage.getValue(SparseStorage.java:70)
at com.snc.pa.dc.Row.getValue(Row.java:204)
at com.snc.pa.dc.DCIndicator.match(DCIndicator.java:320)
at com.snc.pa.dc.DataCollector.map(DataCollector.java:1231)
at com.snc.pa.dc.DataCollector.collect(DataCollector.java:626)
at com.snc.pa.dc.DataCollector.collect(DataCollector.java:477)
at com.snc.pa.dc.DataCollector.collect(DataCollector.java:364)
at com.snc.pa.dc.DataCollectorJob.collect(DataCollectorJob.java:382)
at com.snc.pa.dc.DataCollectorJob.collectWithMutex(DataCollectorJob.java:269)
at com.snc.pa.dc.DataCollectorJob.execute(DataCollectorJob.java:254)
at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:115)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:118)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:102)
at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:300)
at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:188)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:188)
at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:102)

[Logan Poynter]

Can you give some more details on the indicator/job this is for? Do you have record collection on your indicator this job is collecting for?

Performance Analytics snapshots are the lists of records (sys_ids) that are collected at the time that the scores for those records are collected. You can read more about the cleaning process here. Basically, this is trying to clean up old snapshots beyond the range limit in the com.snc.pa.dc.keep_snapshots_for property. 

Also, review KB0550063 for possible solutions. 

[Logan Poynter]

Hello,

Was there any other help needed on this? If not, can you please mark my reply as correct so that others who may have this question will see it?

Please mark my answer as correct/helpful if it has helped you.

Thanks,
Logan

[Farrah1]

Thanks, Logan.  This issue seems to be that the indicator data collection runs fine if I leave off the breakdowns I added, but gets errors when I add the breakdowns.  I'll have to research further.  Thanks so much for your help!

[Logan Poynter]

How many breakdowns do you have that you're adding? Have you narrowed it down to a specific one causing? This generally will happen if a breakdown is on a reference field I've found. 

Please mark my answer as correct/helpful if it has helped you.

Thanks,
Logan