Scheduled Job is failing on rotation tables with 'sys_created on' condition - Known Error

Scheduled Job is failing on rotation tables with 'sys_created on' condition Description Scheduled Job is failing on rotation tables with 'sys_created on' condition

Steps to Reproduce

1. Create an indicator source on any rotation table. For example nlq_query_log or sn_devops_processed_inbound_event with the condition - Created - on - Today 2. Create an indicator based on this indicator source. 3. Add the indicator to a scheduled job and Execute now.

We can see that the job is failing with below exception :

Error collecting for 20220329. Clearing the flushed snapshots for job run with log sys_id 3db8dc75872e091092dfb887cebb35b7 java.lang.NullPointerException at com.snc.pa.dc.DataCollector.retrieveRows(DataCollector.java:1139) at com.snc.pa.dc.DataCollector.collect(DataCollector.java:598) at com.snc.pa.dc.DataCollector.collect(DataCollector.java:505) at com.snc.pa.dc.DataCollector.collect(DataCollector.java:384) at com.snc.pa.dc.DataCollectorJob.collect(DataCollectorJob.java:445) at com.snc.pa.dc.DataCollectorJob.collectWithMutex(DataCollectorJob.java:315) at com.snc.pa.dc.DataCollectorJob.execute(DataCollectorJob.java:300) at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:129)

NOTE: the job is not failing if the indicator source condition is on any other field like Updated or Event Created dates.

Workaround This problem is currently under review and has no workaround. To receive notifications when more information will become available, subscribe to this Known Error article by clicking the Subscribe button at the top of this article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.