Job collector error: Fetched too many rows from indicator source Incidents.Open. Allowed

[arvinvisco]

I am encountering the same problem. The way I set up my indicator source has no filters at the indicator source level rather my filters are specifically set at the indicator level for easier maintenance. Before the clone over the weekend I am not getting the error after the clone I am getting this error  

Fetched too many rows from indicator source Incidents.Open. Allowed

I have counter checked this on each indicators and indicator sources. Recreated a new Job collector. Is there any other place that could cause this problem?

This is the indicator source and one of the indicators. Thanks for looking into this.

[arvinvisco]

I also found this related article

https://community.servicenow.com/community?id=community_question&sys_id=9f10d3e5dbdcdbc01dcaf3231f9619b7

[Adam Stout]

The restrictions are on the indicator source, not the indicator.  Add (at least) the active condition to the source.  This source should also be time-boxed (look at the OOTB examples) to ensure it is historically safe.  This one will get you intro performance and potentially data issues (if you try to use it historically). 

[arvinvisco]

Thanks Adam, this seems to resolve the problem.

[Ashby]

If you used the OOTB Indicator Source (Incidents.Open) for incidents and leveraged the associated a breakdown by priority, it would be much simpler from an administration/maintenance perspective.....not to mention provide you with a greater level of flexibility if you wanted to report on other attributes.    Example Setup below.... 

Also....if you are getting an error on the job, you might want to review the com.snc.pa.dc.max_records setting in the sys_properties table.   By default it is set to 5000 records. 

Indicator Source

Automated Indicator 

Indicator - this indicator is set up to only display Critical Priority Incidents 

Example Indicator