|Applies To||RSA Product Set: RSA Via Lifecycle and Governance (RSA Via L&G)|
RSA Version/Condition: 7.0 and up
|Issue||When running a collector with a circuit breaker threshold, rejections are being counted as new objects, regardless of how long they have been in the source data, or how many successful collections they have been a part of.|
As a result, rejections which have been in the source data for multiple data runs can contribute to triggering the circuit breaker for new data.
|Cause||This is working as designed; rejections are always new objects. Rejections represent data that is being collected from the source which we are unable to load into the system, and as such never propagate to our main tables.|
|Resolution||Rejections should represent a security hole to the customer, and the resolution to them triggering the circuit breaker should be to identify and address the rejections. Use the admin errors provided in the failed collection run to identify the cause of the rejections and then modify either the source data or the collector definition to prevent them from being collected.|
|Workaround||As an alternate solution, the circuit breaker threshold can be increased to accommodate the rejections. This is not an ideal solution as rejections also represent additional overhead in the collector processing, since we will continue to try and reprocess this data as long as it is being collected.|
The threshold is configured under the collectors Circuit Breaker tab.